Zum Ende der Metadaten springen
Zum Anfang der Metadaten

You are viewing an old version of this content. View the current version.

Unterschiede anzeigen View Version History

« Vorherige Version anzeigen Version 3 Aktuelle »

Azure Custom Claim

To use the Approval with Azure IDP, we have to define a Custom Claim in Azure IF the SAP User does not exists in the default Azure Fields (like Username == SAP Username).

  1. Navigate to App Registrations and go to the App we just created in the Steps above

  2. If not already done, navigate to API permission and Grant admin consent to xyz

    image-20240902-061533.png

  3. Navigate to “Expose an API” and click on “Add a Scope”
    You have to provide the Application (client) ID, which can be found on the “Overview” page from the Steps above. The name of the Scope can be random, and should look like this in the End:

    e.g. Read your files-20240418-133949.png

  4. Click on “Add a client application”
    Provide here the Client ID (from above) and create the new Scope

    Add a client application-20240418-134040.png


    Now, lick on “add Applications”

  5. Navigate to Manifest (Bottom of the Menu) and replace in the Manifest JSON following values:

    "acceptMappedClaims": null,
     "accessTokenAcceptedVersion": null,

with

"acceptMappedClaims": true,
"accessTokenAcceptedVersion": 2,

Click on Save. This change can take several minutes to have an effect.

  1. Now, navigate to the Overview back and click on “Manage Application in Enterprise Applications”

  2. Navigate to “Single Sign-On” and click on Edit on “Attributes & Claims”

    Pasted Graphic 7-20240418-134305.png

  3. Click on “Add new Claim”

  4. Provide a Token Name and Select the source attribute where the SAP Username is stored

    Namespace-20240418-134359.png

  5. Save the Settings

  6. Now lets try to access the JWT Token with Postman:

    Pasted Graphic 9-20240418-134548.png

  7. Copy the JWT Token and Copy it into https://jwt.io

    Pasted Graphic 10-20240418-134612.png


    You should see the encrypted JWT and the new created token attribute:

    Pasted Graphic 11-20240418-134631.png

  • Keine Stichwörter