DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • What D'Hack Is DPoP?
  • Configuring SSO Using WSO2 Identity Server
  • Using OKTA as Client Provider in Mulesoft
  • Unlocking Seamless Experiences: Embracing Passwordless Login for Effortless Customer Registration and Authentication

Trending

  • How to Submit a Post to DZone
  • 7 Technology Waves I’ve Seen in 30 Years of Software — Will AI Be the Next Real Transformation?
  • Implementing Secure API Gateways for Microservices Architecture
  • Implementing Observability in Distributed Systems Using OpenTelemetry
  1. DZone
  2. Software Design and Architecture
  3. Cloud Architecture
  4. Configuring Anypoint Platform as an Azure AD Service Provider SSO

Configuring Anypoint Platform as an Azure AD Service Provider SSO

The article will help you through basic knowledge for incorporating Azure AD as an external Identity Provider to the Anypoint platform.

By 
Ashish Jain user avatar
Ashish Jain
·
Aug. 11, 21 · Tutorial
Likes (3)
Comment
Save
Tweet
Share
17.3K Views

Join the DZone community and get the full member experience.

Join For Free

Configure Anypoint platform to use Azure AD as an external identity provider (IDP), including, Single Sign-on (SSO) and the mapping of Azure AD groups to Anypoint platform roles and role groups.

The article will help you through basic knowledge for incorporating Azure AD as an external identity provider to the Anypoint platform. It will also help to set the basic integration and SSO setup between Azure AD and the Anypoint platform.

Before we start, keep in mind that the Relying Party Trust will need to be created manually as we do not provide a metadata file (nor is its use supported). 

Pre-Requisites:

•    An Azure AD account

•    An Anypoint Platform Account

Azure AD Configuration

Step 1: In the Azure portal, select Azure Active Directory as below:

Azure Active Directory Icon

Step 2: Now go to Enterprise applications from the left menu. Select “+ New Application” and then select “+ create your own application”.  

Creating New Azure AD Application

Create New Azure AD application

Adding New Azure AD Application

Add New Azure AD Application

Creating an Azure AD app for Anypoint Platform

Create an Azure AD app for Anypoint Platform


Step 3:  From the add application screen on the right-hand side give it an identifying name and select the option “Integrate any other application you don't find in the gallery (Non-gallery)” and click “create”

Creating Azure Ad app with all details filled in

Creating Azure Ad app with all details filled in


Step 4:  From the newly created application, head over to Single Sign-on and then select SAML as a Single sign-on method

Azure AD Single Sign-On

Azure AD Single Sign-On


SAML as Single Sign-On

SAML as Single Sign-On


Step 5:  From the “Set up Single Sign-On with SAML” Screen, configure the settings: 

  • Click on Edit in the “Basic SAML configuration” card
  • Fill in the required details as below table :

Property

Value

Identifier (Entity ID)

<Org domain>.anypoint.mulesoft.com, where is the Organization domain of your Anypoint Platform organization. Example: my-example-org.anypoint.mulesoft.com

Reply URL

https://anypoint.mulesoft.com/accounts/login/receive-id

Sign-on URL

<leave blank>

Relay State

<leave blank>

Logout URL

<leave blank>

Basic SAML Configuration

Basic SAML Configuration


Step 6:  Capture the User Access URL from Properties Tab. It will be used in Any Point platform Configuration. Azure AD App Properties

Azure AD App Properties


Step 7:  Gather all required information from the “User Attributes and Claims” card. This information will be provided to the Anypoint platform to identify the user. You can also edit this information and capture using the “Edit” on this card.

Within User Attributes & Claims, an initial set of attributes are listed with default values are provided for each property. The attributes and claims listed here appear in the SAML 2.0 token which is sent to Anypoint Platform. The initial attributes can be changed, and new ones added or removed, as required by your organization. The SAML 2.0 IdP configuration within Anypoint Platform allows claims to be specified for the following attributes:

  •  Username (defaults to NameID if no value is provided)
  • First Name
  • Last Name
  • Email
  • Group (Anypoint Platform expects the claim specified here to list the user’s group memberships) 

User Attributes and Claims


User Attributes & Claims
Capture the details/links like “Unique User Identifier (Name ID), user.givenname, user.userprincipalname, user.surname, user.emailaddress ”


Note: that by default, there is no claim specified in User Attributes & Claims for stating the user’s group memberships. If you intend to map Azure AD groups to platform roles and role groups as described above, a claim must be added here. This has the effect of groups to which the user belongs in the SAML token generated by Azure AD and sent to Anypoint Platform. Add a Group claim by following these steps:

  1. Click on the pencil icon to edit the User Attributes & Claims
  2. Select add a group claim
  3. Select the option to return either All groups or Groups assigned to the application in the claim (select the most appropriate of these two options for your organization)
  4. Select Group ID as the source attribute
  5. Click Save 
  6. Click the Close (X) icon to return to the SAML-based Sign-on screen. Verify that there is a claim called Group listed in the User Attributes & Claims section.

Step 8:  Download the Metadata XML from the “SAML Signing Certificate” card. This XML can be directly uploaded to the Anypoint Platform.

SAML-based Sign-On

SAML-based Sign-On


Anypoint Platform Configuration

Step 1: Log in to Anypoint Platform, select Access management and go to “Identity Providers”. Select “SAML 2.0” from the dropdown.

Anypoint platform Access Management

Anypoint platform Access Management


Step 2: Upload the Metadata XML downloaded from Azure AD setup into “Import IdP Metadata”. You will see the metadata is populated automatically. Now we need to change and fill few fields

Configuring Azure AD as Anypoint Identity Provider

Configuring Azure AD as Anypoint Identity Provider


Step 3: Configure the details corresponding to the below table: 

Field

Value

Sign-On URL

The value from the Enterprise app’s User access URL property. The previous section describes how to obtain this value in Azure Portal. This is Obtained in Step 6 of Azure AD Configuration

Sign Off URL

https://login.microsoftonline.com/common/wsfederation?wa=wsignout1.0. This URL can be used to send the Single Log-Out request to, so users both sign out of the Anypoint Platform and have their SAML user’s status set to sign out.

Issuer

<leave as Is>

Public Key

<leave as Is>

Audience

The value from the Identifier (Entity ID) field, displayed under “Basic SAML Configuration” for the Enterprise app in Azure Portal (created in Step 5 of Azure AD Configuration). Example: my-example-org.anypoint.mulesoft.com

Username Attribute

Copy the link for this attribute obtained from Step 7 in Azure AD Configuration. It should be a link for user.userprincipalname.

Example: http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name

First Name Attribute

Copy the link for this attribute obtained from Step 7 in Azure AD Configuration. It should be a link for user.givenname.

Example: http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname

Last Name Attribute

Copy the link for this attribute obtained from Step 7 in Azure AD Configuration. It should be a link for user.surname.

Example: http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname

Email Attribute

Copy the link for this attribute obtained from Step 7 in Azure AD Configuration. It should be a link for user.mail.

Example: http://schemas.xmlsoap.org/ws/2005/05/identity/claims/ emailaddress

Group Attribute?

View the SAML payload to identify the claim which holds the username. Copy and paste the claim into this attribute. Example: http://schemas.microsoft.com/ws/2008/06/identity/claims/groups

Enable new non-SSO users

Optional: check or uncheck the checkbox as required. Note that this has no effect on pre-existing non-SSO users.

Require encrypted SAML assertions

Optional: check or uncheck the checkbox as required. If you want to enforce that only encrypted SAML assertions are accepted, check this box, and configure SAML token encryption in Azure AD accordingly


Test the Configuration

Save changes and test. The following approaches can be used to test – 

  1. Use the test feature from within the Enterprise app in Azure Portal 
  2. Access the User access URL (starts with https://myapps.microsoft.com/…). This is the URL obtained from the Enterprise application’s properties in the section above. 
  3. Access https://anypoint.mulesoft.com/accounts/login/ where is the Organization domain as stated in your Anypoint Platform organization record (visible from within Access Management). Example: https://anypoint.mulesoft.com/accounts/login/my-example-org

Creating Groups and Mapping Roles

  1. Create a group in Azure Ad Users and Groups tabAzure Ad Users and Groups tab
  2. Add new Claim as groups and give the group NameNew Claim as Groups
  3. Create a Role in the Anypoint platformRole in the Anypoint platform
  4. Go inside the Role and click on External Group mapping and add the group created from Azure ADExternal Group Mapping
  5. Add the group to the Identity Provider tab in the Anypoint platformIdentity Provider Tab

 

Test the setting and bingo!



azure ADS (motorcycle) Attribute (computing) Service provider security authentication application app Links Property (programming)

Opinions expressed by DZone contributors are their own.

Related

  • What D'Hack Is DPoP?
  • Configuring SSO Using WSO2 Identity Server
  • Using OKTA as Client Provider in Mulesoft
  • Unlocking Seamless Experiences: Embracing Passwordless Login for Effortless Customer Registration and Authentication

Partner Resources

×

Comments

The likes didn't load as expected. Please refresh the page and try again.

  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook