ºÚÁϺ£½Ç91Èë¿Ú

Integrate with MuleSoft Anypoint Platform

Use ºÚÁϺ£½Ç91Èë¿Ú SAML Single Sign On (SSO) to give your users convenient but secure access to all their web applications with a single set of credentials.

Read this article to learn how to integrate with MuleSoft Anypoint Platform. 

Prerequisites

  • A ºÚÁϺ£½Ç91Èë¿Ú administrator account
  • ºÚÁϺ£½Ç91Èë¿Ú SSO Package or higher or SSO à la carte option
  • A MuleSoft Anypoint Platform user account with Organization Administrator permissions
  • Your MuleSoft Anypoint Platform Organization name

Creating a new ºÚÁϺ£½Ç91Èë¿Ú Application Integration

  1. Log in to the .
  2. Go to USER AUTHENTICATION &²µ³Ù;ÌýSSO Applications.
  3. Click + Add New Application.
  4. Type the name of the application in the Search field and select it.
  5. Click Next.
  6. In the Display Label, type your name for the application. Optionally, you can enter a Description, adjust the User Portal Image and choose to hide or Show in User Portal.

Note:

If this is a Bookmark Application, enter your sign-in URL in the Bookmark URL field.

  1. Optionally, expand Advanced Settings to specify a value for the SSO IdP URL. If no value is entered, it will default to https://sso.jumpcloud.com/saml2/<applicationname>.

Warning:

The SSO IdP URL is not editable after the application is created. You will have to delete and recreate the connector if you need to edit this field at a later time.

  1. Click Save Application.
  2. If successful, click:
    • Configure Application and go to the next section
    • Close to configure your new application at a later time

Configuring the SSO Integration

To configure ºÚÁϺ£½Ç91Èë¿Ú

  1. Create a new application or select it from the Configured Applications list.
  2. Select the SSO tab.
  3. Replace any instances of YOUR_ORGANIZATION with your MuleSoft organization name.
  4. Add or change any desired attributes.
  5. °ä±ô¾±³¦°ìÌýsave.

Download the certificate

  1. Find your application in the Configured Applications list and click anywhere in the row to reopen its configuration window.
  2. Select the SSO tab and click IDP Certificate Valid > Download certificate.

Tip:

The certificate.pem will download to your local Downloads folder.

To configure Mulesoft AnyPoint Platform

  1. Log in to Anypoint Platform using an account that has the Organization Administrator permission.
  2. In the navigation bar or the main Anypoint Platform page, click Access Management.
  3. In the Access Management navigation menu, click Identity Providers.
  4. Select Identity Providers > SAML 2.0.
  5. In the Configurations tab, complete the required fields of the Identity Management SAML 2.0Ìý´Ú´Ç°ù³¾:
    • Sign On URL - enter the ºÚÁϺ£½Ç91Èë¿Ú IDP URL
    • Sign Off URL - enter https://console.jumpcloud.com/userconsole
    • Issuer - enter the ºÚÁϺ£½Ç91Èë¿Ú IdP Entity ID
    • Public Key - copy and paste the contents of the certificate downloaded in the previous section
    • Audience - enter the ºÚÁϺ£½Ç91Èë¿Ú SP Entity ID
    • Single Sign-On Initiation:
      • The Service Provider Only option allows only the Anypoint Platform to initiate SSO.
      • The Identity Provider Only option allows only your external identity provider to initiate SSO.
      • °Õ³ó±ðÌýBoth option allows either Anypoint Platform or your external identity provider to initiate SSO. The default value for this setting for newly configured identity provider configurations is Both.
  6. Optionally, expand Advanced settings, and provide the following values:
    • Username Attribute - Field name in the SAML AttributeStatements that maps to username. If no value is configured, the NameID attribute of the SAML Subject is used (Note: this is outside the SAML AttributeStatements).
    • First Name Attribute - Field name in the SAML AttributeStatements that maps to First Name.
    • Last Name Attribute - Field name in the SAML AttributeStatements that maps to Last Name.
    • Email Attribute - Field name in the SAML AttributeStatements that maps to Email.
    • Group Attribute - Field name in the SAML AttributeStatements that maps to Group.
    • Require encrypted SAML assertions - If enabled, the SAML assertions sent from the IdP must be encrypted and follow the guidelines mentioned in the .
  7. °ä±ô¾±³¦°ìÌýCreate.

Using JIT Provisioning

Additional attributes are required to use JIT provisioning. JIT required attributes are prepopulated and are on by default to enable JIT provisioning. You can’t edit the JIT required service provider attributes. You can customize the ºÚÁϺ£½Ç91Èë¿Ú attribute name and the constant value for JIT required attributes. Toggle off the attributes to opt out of sending the attributes in the SAML assertion

To complete the provisioning process

  1. Authorize a user’s access to the application in ºÚÁϺ£½Ç91Èë¿Ú.  
  2. Have the user log in to the application using SSO. The SAML assertion passes from ºÚÁϺ£½Ç91Èë¿Ú to the service provider, and gives the service provider the information it needs to create the user account.

Authorizing User SSO Access

Users are implicitly denied access to applications. After you connect an application to ºÚÁϺ£½Ç91Èë¿Ú, you need to authorize user access to that application. You can authorize user access from the Application Configuration panel or from the Groups Configuration panel. 

To authorize user access from the Application Configuration panel

  1. Log in to the .
  2. Go to USER AUTHENTICATION > SSO Applications, then select the application to which you want to authorize user access.
  3. Select the User Groups tab. If you need to create a new group of users, see Get Started: User Groups.
  4. Select the check box next to the group of users you want to give access.
  5. Click save

To learn how to authorize user access from the Groups Configuration panel, see Authorize Users to an SSO Application.

Validating SSO user authentication workflow(s)

IdP-initiated user workflow

  • Access the
  • Go to Applications and click an application tile to launch it
  • ºÚÁϺ£½Ç91Èë¿Ú asserts the user's identity to the SP and is authenticated without the user having to log in to the application

SP-initiated user workflow

  • Go to the SP application login - generally, there is either a special link or an adaptive username field that detects the user is authenticated through SSO

Note:

This varies by SP.

  • Login redirects the user to ºÚÁϺ£½Ç91Èë¿Ú where the user enters their ºÚÁϺ£½Ç91Èë¿Ú credentials
  • After the user is logged in successfully, they are redirected back to the SP and automatically logged in

Removing the SSO Integration

Important:

These are steps for removing the integration in ºÚÁϺ£½Ç91Èë¿Ú. Consult your SP's documentation for any additional steps needed to remove the integration in the SP. Failure to remove the integration successfully for both the SP and ºÚÁϺ£½Ç91Èë¿Ú may result in users losing access to the application.

To deactivate the SSO Integration

  1. Log in to the .
  2. Go to USER AUTHENTICATION > SSO Applications.
  3. Search for the application that you’d like to deactivate and click to open its details panel. 
  4. Select the SSO tab.
  5. Scroll to the bottom of the configuration.
  6. Click Deactivate SSO
  7. Click save
  8. If successful, you will receive a confirmation message.

To delete the application

  1. Log in to the .
  2. Go to USER AUTHENTICATION > SSO Applications.
  3. Search for the application that you’d like to delete.
  4. Check the box next to the application to select it.
  5. Click Delete.
  6. Enter the number of the applications you are deleting
  7. Click Delete Application.
  8. If successful, you will see an application deletion confirmation notification.
Back to Top

List IconIn this Article

Still Have Questions?

If you cannot find an answer to your question in our FAQ, you can always contact us.

Submit a Case