Skip to main content
P
Peter34950506yidy
Participant
January 22, 2024
Answered

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

  • January 22, 2024
  • 1 reply
  • 1681 views

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

    This topic has been closed for replies.
    Correct answer Peter34950506yidy

    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 Entra ID | Microsoft Learn.
    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.

    1 reply

    P
    Peter34950506yidyAuthor
    Participant
    January 29, 2024

    Nobody who knows the answer on question 2?

     

    P
    Peter34950506yidyAuthorCorrect answer
    Participant
    February 8, 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 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 Entra ID | Microsoft Learn.
    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.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices