2024 Oct 16 5:44 PM - edited 2024 Oct 16 10:24 PM
Hello experts,
I have configured SSO to SAC (IAS as Proxy and Azure as IdP). In SAC, I enabled ‘Dynamic User Creation’ and set the "User Attribute" = email. When I try to verify my user in SAC under Step 4 against Azure AD, I can log in in SAC, but it seems that the user attributes are not being transmitted. It looks like this, see screenshot.
Also, I don’t see the "SAML USER MAPPING" column under Users in SAC.
Why are the user attributes not being transmitted, and how can I enable the "SAML USER MAPPING" column?
Thank you very much !!!
Best Regards
Request clarification before answering.
The SAML mapping column is only shown when you are mapping on a 'custom' value. When mapping on userid or email, then there is no SAML mapping column.
Read my blog here about the problems of using SAML SSO mapped on 'email' with dynamic user creation. Its 'ok', but you don't get the userID of your choice. https://community.sap.com/t5/technology-blogs-by-sap/sap-datasphere-security-amp-data-access-control... (the blog is focused on Datasphere but has a section on userIDs for SAP Analytics Cloud)
To get the USERID of your choice you need to use the SCIM v2 API which is used typically with user provisioning tools (like SAP Identity Provisioning Services) or just direct coding the API with your own solution.
If you have already loads of users with the 'wrong' userID you can use my sample scripts to 'migrate' the user ID. Sample 2666 'Migrate userID' will create a new user off the source, copying all the user properties, like roles/teams etc. You'll also find my user guide for the samples handy to explain some practical and other handy things about the mappings for example.
Overall, you'd be better to map on USERID and ask Azure to return a USERID as the Subject NameID rather than an email. You can still authenticate by identifying yourself by email. Sometimes your userID has funny characters that are not permitted. In which case, manipulate the Subject nameid dynamically.
USERID must not contain unsupported characters, any lowercase character, a ‘-’ or more than 20 characters
Manipulating the NameID when using SAP Identity Authentication, Microsoft Azure, Microsoft ADFS, Okta
Kind regards, Matthew
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Matthew, Hi alexeydugarov
Thanks a lot, for the detailed response. I will study all the links.
@Matthew_Shaw In SAC, I set the user attribute to Custom SAML User Mapping—Is that what you meant in this sentence: "The SAML mapping column is only shown when you are mapping on a 'custom' value. When mapping on userid or email, then there is no SAML mapping column"?
However, I still can't see the option "SAML USER MAPPING" in my SAC tenant. I can't find it under Security/User, and it's also not listed under Security/Roles. Why?
Many Tahnks
Best Regards
Hello @Matthew_Shaw
It works, thank you! I haven’t enabled SSO yet (conversion not done), which is why I didn’t see the SAML Attribute button.
Thanks again!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 14 | |
| 8 | |
| 6 | |
| 6 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.