Unable to enter Tennant URL when setting up SSO User provisioning

Sean S. Duthie 1

As per the following guide from AWS: https://docs.aws.amazon.com/singlesignon/latest/userguide/azure-ad-idp.html

We should see the Tennant URL field, instead we appear to only see the clientsecret & Secret Token fields

SUNOJ KUMAR YELURU 13,936 Reputation points MVP

2021-01-09T05:07:19.17+00:00

Let us know if anything required.

Please don’t forget to "Accept the answer" and up-vote wherever the information provided helps you, this can be beneficial to other community members.
SUNOJ KUMAR YELURU 13,936 Reputation points MVP

2021-01-14T00:33:14.76+00:00

To follow-up, Please let us know if you have further query on this.
Please don’t forget to Accept the answer
SUNOJ KUMAR YELURU 13,936 Reputation points MVP

2021-03-07T04:04:29.443+00:00

To follow-up, Please let us know if you have further query on this.
Please don’t forget to Accept the answer
Kliment Andreev 25 Reputation points

2024-03-11T19:11:05.6766667+00:00

If you see clientsecret instead of Tenant ID means that you are using the wrong AWS application in Entra ID.

There are two apps: AWS Single Sign-on for a single account (you are using that one) and AWS IAM Identity Center (former AWS SSO). The former is for a single account, the later is for AWS accounts in Organization structure.

1 answer

SUNOJ KUMAR YELURU 13,936 Reputation points MVP

2020-12-31T14:53:30.5+00:00

@Sean S. Duthie

Yes, Copied the SCIM endpoint value in AWS SSO and Paste that value into the clientsecret field in Azure AD.

And copied the Access token value in AWS SSO. Paste that value into the Secret Token field in Azure AD.

----------

Please don’t forget to "Accept the answer" and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment