This can be the one you set up using the instructions in either Section 2.0, Setting Up a Basic Access Manager Configuration or Section 2.11, Sample Configuration for Protecting an Application Through Access Manager. These accounts can be federated with the user’s employee account when both companies agree to set up the trusted relationship.Ī basic Access Manager configuration with Identity Server and Access Gateway configured for SSL. Their users have accounts with these companies. For example, most companies have contracts with other companies for their user’s health benefits and retirement accounts. You can set up federation between providers in the same company or between providers of separate companies. The trusted relationship is automatically set up for you when you specify authentication settings for Access Gateway and select an Identity Server Cluster.
When federation is configured to be bidirectional, both sites need to be equally secure.Īccess Gateways in Figure 4-5 are service providers and are configured to use Identity Servers as identity providers. Federation can be configured to go both ways, so that it does not matter whether the user logs into Site A or Site B. This means that users who log in to Site A have access to the resources at Site A and B, but users who log in to Site B have access only to the resources at Site B. In this scenario, Site B is not as secure a site as Site A, so federation is configured to go only one way, from Site A to Site B. After an account has been federated, the user can log in to Site A and access to the resources on the web servers of both Site A and Site B. Both employees and customers authenticate to this site to access to the resources of the web server with the URL of.
Site B is identity provider for the Bugzilla application.
In this configuration, Site A is identity provider for the corporate resources, and the employees authenticate to this site and have access to the resources on the web server with the URL of.
0 kommentar(er)
