![]() On the Connection Configuration page, for Upload Metadata, select the AWS SSO metafile that you downloaded.Ģ.c Configure and then download the application metadata file for PingOne.In the search field, enter AWS and select AWS Single Sign On (SAML with Provisioning).Ģ.b Upload the metadata file that you downloaded in Step 1.Choose Applications and then choose Application Catalog.In PingOne, choose Setup and select the identity repository that you will be using.Step 2: Add the PingOne AWS SSO application to the PingOne admin portal and complete the metadata exchange 2.a Log in to PingOne using your PingOne credentials and navigate to the AWS SSO application If you’re using Workforce360 via PingFederate, see Steps 2 and 3 for Workforce360 via PingFederate. Here’s how to continue with the solution if you’re using Workforce360 via PingOne. Steps 2 and 3 for Workforce360 via PingOne After you have set up your AWS SSO application in either PingOne or PingFederate in the following steps, you will return to the console to upload PingOne or PingFederate’s metadata. In the Configure service provider metadata section, choose Download metadata file and then choose Save file.On the Change identity source page, select External identity provider.On the Settings page, under Identity source, choose Change.In the navigation pane, choose Settings.Sign in to the AWS Management Console and open AWS Single Sign-On.This step is the same for both solutions. Step 1: Download the AWS SSO metadata file A configured identity repository in PingOne or identity provider in PingFederate.You can also sign up for a free PingOne trial. ![]() If you don’t have an existing account, you can subscribe to Ping Identity in AWS Marketplace.
0 Comments
Leave a Reply. |