• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
1

Adobe Identity Management (SAML) 2 questions about OIDC and provisioned user attributes

Community Beginner ,
Jan 22, 2024 Jan 22, 2024

Copy link to clipboard

Copied

Good afternoon Adobe community,

Question 1
When creating the Azure Enterprise application Adobe Identity Management (SAML) according to https://learn.microsoft.com/en-us/entra/identity/saas-apps/adobe-identity-management-tutorial, the add domain step is also created the Azure Enterprise application Adobe Identity Management (OIDC).
What is this used for or can it be thrown away?

Question 2
The display name of the Federated account is incorrect. Should be displayname. Now the example shows 'Peter Laarse, van der' instead of Laarse, Peter van der.
How do you add display name, or else how do we get accounts with prefixes neatly?

 

I hope someone has experience with this an is able to answer these questions.
Thanks in advance

Peter van der Laarse

TOPICS
Enterprise , Identity and SSO , Manage account

Views

164

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Community Beginner , Feb 08, 2024 Feb 08, 2024

I made a ticket at Microsoft after Adobe support advised me to do so. Microsoft provided me with the following answer
Below is a summary of the support request for your records:
Symptom:  User Display name does not provision properly with Adobe Identity Management (SAML)

Cause: Adobe Identity Management does not have such attribute Display Name as it into Azure. 

Resolution: With this in mind, please understand that the attributes selected for the schema are not subject to change on our end, or on y

...

Votes

Translate

Translate
Community Beginner ,
Jan 29, 2024 Jan 29, 2024

Copy link to clipboard

Copied

Nobody who knows the answer on question 2?

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Feb 08, 2024 Feb 08, 2024

Copy link to clipboard

Copied

LATEST

I made a ticket at Microsoft after Adobe support advised me to do so. Microsoft provided me with the following answer
Below is a summary of the support request for your records:
Symptom:  User Display name does not provision properly with Adobe Identity Management (SAML)

Cause: Adobe Identity Management does not have such attribute Display Name as it into Azure. 

Resolution: With this in mind, please understand that the attributes selected for the schema are not subject to change on our end, or on yours, but are pre-configured by the application publisher. Please review the following document for further context: Tutorial - Customize Microsoft Entra attribute mappings in Application Provisioning - Microsoft Entr....
For us the only thing we can do is accept this issue and explain it to our users.

The answer on question 2 about the exra OIDC application was:

It is not safe to delete the Adobe Identity Management (OIDC) if you have configured SSO in Adobe Identity Management (SAML).
The OIDC is used to authenticate users who are not part of the SAML identity provider. If you delete the OIDC, users who are not part of the SAML identity provider will not be able to authenticate. 
So i think it is safe te delete it if you only use your own Azure as the SAML identity provider, but wel leave it.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines