![]() This blog post uses Okta and AWS Identity Center as the example IdPs, but the steps apply for any SAML 2.0 compliant identity providers. Test SSO using both IdP applications with Amazon Connect.Configure the SAML IdP application to utilize the amended role for Amazon Connect.Re-Use the existing IAM role that is being used with the existing SAML IdP by updating the trust relationship to include the new IdP.Create an identity provider reference in AWS IAM for the additional SAML IdP.Create an Amazon Connect SSO Application for the additional SAML identity provider (IdP) in your SSO environment.This blog post details the steps required to configure additional identity providers for a single Amazon Connect instance.īelow is a summary of the steps required to configure an additional IdP for your Amazon Connect Instance: Companies often have multiple identity providers (IdPs) within their environment, either serving different applications with their own unique use case or as a backup mechanism if their primary IdP fails. This enables users to access multiple applications securely via a single ID and password.īy default, Amazon Connect allows a 1:1 mapping from an Amazon Connect instance to an identity provider (IdP). Identity management for an Amazon Connect instance can be configured in one of the three ways:Īmazon Connect supports identity federation with Security Assertion Markup Language (SAML) 2.0 to allow web-based single sign-on (SSO) from your organization to your Amazon Connect instance. through cookies) so it does not have to authenticate with the IdP on every request.Identity management is a framework of policies and technologies to ensure that the right users have the appropriate access to technology resources. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |