If the Sitecore Content Management instance can be accessed by multiple host names, what would you do to enable users for each site to be able to log in to the Sitecore shell?
A.
Patch the web.config for the Content Management instance with the required permission groups.
B.
Update the role for each user group to include the appropriate site permissions.
C.
Remove all specific host names from the Identity Server configuration settings file and replace them with wild-card options.
D.
Add AllowedCorsOriginsGroup for each site to the Identity Server configuration.
If the Sitecore Content Management instance can be accessed by multiple host names, you need to add AllowedCorsOriginsGroup for each site to the Identity Server configuration. This will enable the users for each site to be able to log in to the Sitecore shell using the Identity Server. The AllowedCorsOriginsGroup element defines a group of URIs that are allowed to make cross-origin requests to the Identity Server. You can use multiple subnodes to define more than one URI, or you can use the | symbol to separate URIs within a node. You can also use the {AllowedCorsOrigin} template to simplify the configuration. When you use that template, all origins (hosts) are notified about the sign-out1. References:
Single sign-out
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit