To integrate your company's SSO (Single Sign-on) to GovCloud Anypoint Platform using SAML 2.0
Once you have open a case with support you will need to upload the following information about your SSO. Work with Identity Provider Admin to get the information.
Sign On URL* :
Sign Off URL* :
Issuer* :
( In the case of Salesforce IDP "EntityID" in the IDP metadata is same as Issuer.)
Public Key* :
Audience* :
(arbitrary string that identifies your Anypoint Platform organization. Typical value for this string is <organizationDomain>.gov.anypoint.mulesoft.com. Entity ID in the case of Azure)
(Optional)
Username Attribute :
(NameID attribute from the Subject block is used in the SAML assertion if left empty)
First Name Attribute :
(firstname attribute is used in the SAML assertion if left empty)
Last Name Attribute :
(lastname attribute is used in the SAML assertion if left empty)
Email Attribute :
(email attribute is used in the SAML assertion if left empty)
Group Attribute :
If no optional attributes are submitted, then you must send "email", "firstname", "lastname" in the attribute claims. Once all the necessary information is provided we can then process with your SSO configuration.
If a signing certificate is needed for single logout or encrypted SAML assertion:
https://docs.mulesoft.com/access-management/conf-saml-sso#generate-a-new-key
The ACS URL
Please note that the assertion consumer service (ACS) URL is generated when when MuleSoft configures the external IDP on MuleSoft side. This will be shared with you and you need to update at IDP side
By default -https://gov.anypoint.mulesoft.com/accounts/login/:org-domain/providers/:providerId/receive-id.
For all new configurations please use above URL. Please note :org-domain and :providerId are just placeholders for actual values.
If encryption is not required it can work with either above or previous legacy url https://gov.anypoint.mulesoft.com/accounts/login/receive-id).
001117140

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.