K2 blackpearl Installation and Configuration Guide > Installation > Installing a standalone system > Resolve Security Token Service Issuers | Send feedback |
This panel will only appear when there has been more than one K2 site (for example Workspace, Designer or Runtime site) registered on the farm. |
If you are using Claims or have an environment with multiple domains you would have more than one potential Security Token service Issuer and this panel gives you the opportunity to choose which to use with K2.
Example: You may have an environment with a DMZ set up for certain users outside your company to access parts of your K2 environment but internal Issuers set up for your company users to access everything.
If the selected IIS binding in the Bindings panel does not match the URI for the Security Token Service in the K2 database Identity.ClaimIssuer table, you will need to resolve which STS issuer to use. You do this by making a choice on the Resolve Security Token Service Issuers Panel. For more information on the IIS Bindings see the topic: Workspace Web Site Configuration panel for either the Standalone installation or the Custom installation.
The STS URI may be different for these reasons:
|
If you want to change the bindings for your sites, it is strongly recommended to run the K2 blackpearl Setup Manager. This will ensure that the environment library fields and the bindings / STS configuration remain in sync. Using the K2 Management page is the only other supported option. |
|
Existing claims tokens may be invalidated if you leave the Update box checked. NOTE: Update will be checked by default. |