- 最新
- 最多得票
- 最多評論
I think I have found the solution. I removed the Emails[type eq "work"]value and PhoneNumbers[type eq "work"]value attributes from the user provisioning. I was able to then provision the user and login as them.
I have come across the exact same issue... tried multiple times but no joy.
Like yourself when I remove the user from the Azure AD side, I get the correct message.
I have also enabled Automatic provisioning and can see AzureAD user provisioned into AWS Identity centre, but I still cannot login
I am having this exact same issue using Okta. I followed the setup steps multiple times verbatim and am met with this opaque error. I also tried not mapping the emailType and phoneType attributes as suggested above.
Any help here would be truly appreciated. This is a huge blocker for us.
相關內容
- 已提問 6 個月前
- AWS 官方已更新 1 年前
- AWS 官方已更新 3 年前
- AWS 官方已更新 3 年前
- AWS 官方已更新 5 個月前
From where did you remove that?
On the enterprise app in Azure > Provisioning > Edit Attribute Mappings > Mappings > Provision Azure Active Directory Users
that hasn't worked for me, can I ask how you were able to identify those to problem attributes?
It is mentioned in the troubleshooting steps of this documentation: https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/active-directory/saas-apps/aws-single-sign-on-provisioning-tutorial.md#troubleshooting-tips