Step 1: Copy
the SAML Configurations from Identity as a ServiceMuleSoft offers an integration platform helping businesses connect data, applications and devices across on-premises and cloud computing environments (see https://www.mulesoft.com/). You can protect access to MuleSoft by integrating MuleSoft with Identity as a Service. Once integrated, users can use single sign-on to log in to their MuleSoft account through Identity as a Service.
Note: This integration was tested using Identity as a Service version 5.14 and MuleSoft Anypoint Platform Private Cloud Edition 3.0.0. Other versions of MuleSoft may require integration and configuration steps that differ from those documented in this procedure. For other versions of MuleSoft, this integration guide may be used as an initial approach for integrating MuleSoft. In the event of other issues, contact support@entrust.com for assistance.
Step 1: Copy
the SAML Configurations from Identity as a ServiceCopy the SAML Configuration from Identity as a Service
1. Log into your Identity as a Service administrator account.
2. Click
> Security
> Applications. The Applications Lists page appears.
3. Under SAML Cloud Integrations, click SAML Configuration. The SAML Configuration dialog box appears.
This dialog box contains information you need to configure your SAML application for Identity as a Service authentication.
4. Do one of the following:
● Leave this dialog box open to reference later in this procedure.
● Copy the Entity ID, Single Sign-on URL, and Single Logout URL to a text file and save it to reference later in this procedure.
Note: Depending on the integration you are performing, you may not need all three of these SAML configuration values.
Step 2: Export
the signing certificate from Identity as a ServiceExport a SAML signing certificate
1. Log in to your Identity as a Service administrator account.
1. Click
> Security > Applications.
The Applications List page appears.
2. Under SAML Cloud Integrations, click SAML Signing Certificates. The SAML Signing Certificates page appears.
3. Click
next to the certificate to export the certificate
you want to import into your SAML service provider application. The Export Certificate dialog box appears.
a. If the certificate has been issued by a CA, do one of the following:
– Click Certificate to export the self-signed certificate.
– Click Root CA Certificate to export a certificate issued from a CA.
– Click Certificate Chain to export the SAML signing certificate and its CA certificates.
b. Click Export.
Step
3: Add Identity as a Service as an Identity Provider in MuleSoft 1. Log in to your MuleSoft Anypoint Platform as an administrator. The Anypoint Platform page appears.
2. Click
> Access Management.
The Access Management page appears.
3. Click Organization. The Organization page appears.
4. Click Add Business Group. The Organization info dialog box appears.
5. Enter the following organization information:
a. Name
b. Domain
c. Owner
d. Client id provided by to you by MuleSoft
e. Client Secret
6. Optional: Modify the Default session timeout.
7. Click Save.
8. In the Access Management menu, click Identity Providers. The Identity Providers drop-down list appears.
9. Select SAML 2.0 from the Identity Providers drop-down list. The Identity Provider Configuration page appears.
10. In the Sign-On URL field, enter the Single Sign-On URL you copied from Step 1: Copy the configuration from Identity as a Service.
11. In the Sign Off URL field, enter the Single Logout URL you copied from Step 1: Copy the configuration from Identity as a Service.
12. In the Issuer field, enter the Entity ID you copied from Step 1: Copy the configuration from Identity as a Service.
13. Open the certificate file that you downloaded in Step 2: Export the signing certificate from Identity as a Service.
14. In the Public Key field, paste the contents of the signing certificate.
15. In the Audience field, enter the string that identities your Anypoint Platform organization.
Example:
<organizationDomain>.anypoint.mulesoft.com
where organizationDomain is the Domain
you entered in step 5e.
16. For the Single Sign-On initiation, select Both.
17. Click Create.
Step
4: Download the metadata from MuleSoft Anypoint1. Log in to your MuleSoft Anypoint Platform as an administrator. The Anypoint Platform page appears.
2. Click
> Access Management.
The Access Management page appears.
3. In the Access Management menu, click Identity Providers. The Identity Providers page appears.
4. Click Edit next to SAML 2.0. The Identity Provider Configuration page appears.
5. Click Anypoint service provider metadata. The metadata downloads in an XML file format. You need this file for Step 4: Add MuleSoft to Identity as a Service.
Step
5: Add MuleSoft to Identity as a ServiceAdd MuleSoft as an application to Identity as a Service
1. Log into your Identity as a Service administrator account.
2. Click
> Security > Applications. The Applications
Lists page appears.
3. Click Add. The Select an Application Template page appears.
4. Under SAML Cloud Integrations, click MuleSoft. The Add MuleSoft page appears.
5. Enter an Application Name.
6. Enter an Application Description.
7. Optional. Add a custom application logo.
a. Click 
next to Application Logo. The
Upload Logo dialog box appears.
b. Click 
to
select an image file to upload.
c. Browse to select your file and click Open. The Upload Logo dialog box reappears showing your selected image.
d. If required, resize your image.
e. Click OK.
8. Select the Authentication Flow that appears to users during login.
9. Click Next. The General page appears.
10. Click
to the Upload Metadata XML
and browse to the location of the metadata file you downloaded
in Step 4: Download the metadata file from MuleSoft. The Metadata
Configuration dialog box appears.
a. If required, click Merge with existing values to merge new values with existing values for Alternative Assertion Consumer Services URLs and SAML attribute names.
b. Click Save.
11. Optional. Enter the SAML Username Parameter Name used to identity the user ID being requested for authentication. The user ID can then be passed as a parameter, for example, Username=jdoe. Alternately, if the SAML username is NameID, the SAML Request XML NameID element value is used to the identify the IDaaS userID.
12. Enter the SAML Session Timeout to the time when the SAML Assertion times out. The maximum is 720 minutes.
13. From the SAML NameID Attribute drop-down list, select Email.
14. From the SAML NameID Encoding Format drop-down list, select Unspecified.
15. Select the SAML Signing Certificate from the drop-down list.
16. Select Sign Complete URL Response.
17. Deselect Enable Go Back Button if you do not want users to be able to go back to the MuleSoft login page to log in.
18. Select Show Default Assertion Consumer URL Service in the My Profile. When selected, the Default Assertion Consumer URL appears in a user's My Profile page in addition to relay states and Alternative Assertion Consumer URLs.
19. Optional. Select Encrypt SAML Assertion. If you select this option, do the following:
c. From the Encryption Method for Key drop-down list. select RSA-OAEP.
d. Click
Encryption Certificate File
and browse to select the Mule Soft certificate file used to encrypt
the SAML assertion.
20. Optional. Add Alternative Assertion Consumer Service URLs, as follows:
a. Click Add.
b. Enter a Name.
c. Enter a URL Value.
d. Select Show in My Profile to display the Alternative Consumer Service URL in a user's My profile page.
e. Optional. Add an Application Logo.
f. Click Add.
g. Repeat these steps to add more Alternative Assertion Consumer Service URLs.
21. Add a Relay State, as follows:
a. Under Relay State click Add. The Add Relay State dialog box appears.
b. Enter a MuleSoft Anypoint as the Name for the relay state.
c. Copy the Assertion Consumer Service URL and paste it in the Value field for the relay state. This setting specifies the application or URL that a user is redirected to after successful authentication. The Relay states appear on the user's My Profile page.
d. Optional.
Add a Relay State custom logo.
Click next
to Relay State Logo. The Upload
Logo dialog box appears.
Click
to select an image file to upload.
Browse to select your file and click Open. The Upload Logo dialog box reappears showing your selected image.
If required, resize your image.
Click OK.
e. Click Add.
Notes: After
you add relay states, you can also enable or disable them on the Add/Edit
application page. Click 
next to the relay state to disable it or click 
to re-enable it.
Relay states apply to the Default Assertion Consumer Service URLs and
not the Alternative Consumer Service URLs.
22. Include the user attributes for email, firstname, and lastname in the SAML assertion, as follows:
Add an email user attribute
f. Under SAML Attributes, click Add. The SAML Attributes dialog box appears.
g. Enter email in the Name field.
h. Click Add next to Value(s).
i. In the Values field type < and select <Email> to include a user's email every time the user authenticates to the application.
j. Click Add.
Add a first name user attribute.
a. Under SAML Attributes, click Add. The SAML Attributes dialog box appears.
b. Enter first name in the Name field.
c. From the drop-down list, select the Name Format for the attribute.
d. Click Add next to Value(s).
e. In the Values field type < and select <First Name> to include a user's first name every time the user authenticates to the application.
f. Click Add.
Add a last name user attribute.
a. Under SAML Attributes, click Add. The SAML Attributes dialog box appears.
b. Enter last name in the Name field.
c. From the drop-down list, select the Name Format for the attribute.
d. Click Add next to Value(s).
e. In the Values field type < and select <Last Name> to include a user's Last Name every time the user authenticates to the application.
f. Click Add.
23. Click Submit.
Step 6: Create
a resource rule to protect access to MuleSoftCreate a resource rule to protect access to a SAML application
1. Log in to your Identity as a Service administrator account.
2. Click
> Security
> Resource Rules. The Resource Rules List
page appears.
3. Click + next to the application you want to protect with a resource rule. The Add Resource Rules page appears.
4. Enter a Rule Name and Rule Description for the resource rule.
5. In the Groups list, select the group or groups of users restricted by the resource rule.
These are the groups to which the resource rule applies. If you do not select any groups, by default the resource rule applies to all groups.
6. Click Next. The Authentication Conditions Settings page appears.
7. Optional: Select Disable Single Sign-On for Application to force a user to re-authenticate whenever they attempt a new login.
8. If you do not Enable Advanced Risk Factors, do the following:
a. Select the Authentication Flow from the drop-down list. The Authentication Flow flowchart updates based on the selection.
b. Click Submit to save the Resource Rule.
9. If you want to Enable Advanced Risk Factors, complete the remaining steps in this procedure.
10. Select Enable Advanced Risk Factors to add additional risk factors to the resource rule.
11. Select Enable Strict Access for Application to set the resource rule to deny access regardless of the outcome from other resource rules. If this option is disabled for any resource rule that denies access, the user is allowed access if at least one resource rule allows access.
12. For each Advanced Risk Factor, click the Deny option to deny access to the application if the risk factor fails regardless of the results of the other risk factors.
13. Click Date/Time to set the conditions as follows:
a. Select one of the following:
– Allow Date/Time to set when a user can access the application.
– Deny Date/Time to set when the user cannot access the application.
The Date/Time Context Condition Settings appear.
b. Select the Condition Type:
– Specific Date Range Condition—Allows or denies access to the application during a select period of days.
– Time-of-day and/or Day of Week Recurring Conditions—Allows or denies access to the application on a specific time of day, day of the week, or both. Recurring times selected only apply to days not denied.
– Clear Selection—Clears existing Date and Time conditions.
c. Set the Condition Type settings, as follows:
i) Select Use local time zone to use the local time zone or deselect Use local time zone to use the local time zone and begin typing the time zone in the Begin Typing Timezone name field and select the time zone from the drop-down list.
ii) If you selected Specific Date Range Condition, click Start Date to select a start date from the pop-up calendar. Optionally, select the End Date.
iii) If you selected Time-of-Day and/or Day-of-Week, click Start Time and select the start time from the pop-up clock. Optionally set the End Time. You must also select the days of the week for the condition.
d. Click Save to return to the Authentication Conditions Settings page.
14. Click Geolocation to set the Location Condition Settings, as follows:
a. Select Allow or Deny to create an allowed or denied country list.
b. From the Selected Countries drop-down list, select the countries to add or deny access to the application. Repeat until you have added all the desired countries to the list.
c. Select Allow Anonymous IP Address to increase the risk of users authenticating from an anonymous IP.
d. Click Save to save to return to the Authentication Conditions Settings page.
15. Click Source IP Address. The IP Address Risk Setting dialog box appears. Do one of the following:
a. Select Custom and add the required IP Allowed Addresses and IP Denied Addresses.
b. Select IP List Address and select the IP List to allow or deny.
c. Select None to not restrict any IP addresses.
d. Click OK to return to the Authentication Conditions Settings.
16. Click Machine Authentication to set the Machine Authentication Condition Settings, as follows:
a. Set the Machine Authentication Risk is less than or equal to the value that the machine authenticator's total risk score must be less than during authentication to pass this condition.
The risk score is based on the attribute differences
between a user's Machine Authentication information and that recorded
on Identity as a Service before the condition fails. If an attribute does
not match, the attribute incurs the number of risk points shown in Non-Matching Risk Points for that attribute. The
Non-Matching Risk Points values of each non-matching
attribute are added together, resulting in a total risk score. This score
is normalized to be out of 100 as follows:
Total Risk Score = (Total Risk Points
of Failing Attributes / Maximum Risk Points of All Enabled Attributes)
* 100
The resource rule condition fails when the number of non-matching risk
points exceeds the Machine Authentication Risk value defined in this step.
A value of 0 means that a single attribute
difference causes the Device Fingerprint
condition to fail. The default value is 3.
The value between 0-50 can be entered.
The default value is defined by the Machine Risk Limit.
See Modify machine authenticator settings.
b. Click Save.
17. Define the Location History / Known Locations and Travel Velocity conditions. The Risk-Based Authentication (RBA) settings of your Identity as a Service account define the location history and travel velocity conditions. See Manage risk-based authentication settings for more information.
18. Set the Device Certificates risk factor to require the client to perform client-authenticated SSL with a certificate issued from a trusted CA to pass.
19. Set the risk score for application conditions to set the risk percentage a user receives if they fail to meet the condition, as follows:
● Click the dot next to the condition setting and slide the risk scale to the risk percentage
-or-
● Click the 0% and enter the risk points and then click OK.
The default setting is 0%. The Risk percentage determines the authentication requirements as set by the Authentication Decision. When a user attempts to authenticate to an application, the final risk percentage is the sum of all failed conditions.
20. Set the Authentication Decision risk level for Medium Risk and High Risk as follows:
a. Click the risk threshold percentage to the right of Medium Risk or High Risk. The Risk Threshold dialog box appears.
b. Enter the risk percentage.
c. Click OK.
21. Select the Authentication Flows for Low Risk, Medium Risk, and High Risk from the drop-down lists. The Authentication Flows flowchart updates based on your selections.
22. Click Submit to create the resource rule.
Testing Service Provider Login
1. Open a Web browser and enter the URL for your MuleSoft Anypoint account. You are directed to Identity as a Service.
2. Enter your MuleSoft Anypoint account User ID and click Next.
3. Respond to the second-factor authentication challenge. If you respond successfully, you are logged in to the MuleSoft Anypoint Home page.
Testing Identity as a Service redirect log in
1. Log in to your Identity as a Service account.
2. Go to your My Profile page if you are not already there.
3. Under Applications, click MuleSoft Anypoint.
4. Respond to the second-factor authentication challenge. If you respond successfully, you are logged into MuleSoft Anypoint.