Step 1: Copy
the SAML Configuration from Identity as a ServiceMimecast is a cloud subscription service that combines solutions for email security, archiving, and continuity. See https://www.mimecast.com/. You can protect access to Mimecast by integrating Mimecast with Identity as a Service. Once integrated, users can use single sign-on to log in to their Mimecast account through Identity as a Service.
Note: This integration was tested using Identity as a Service version 5.33 and Mimecast v1.7.0-20230611_2243. Other versions of Mimecast may require integration and configuration steps that differ from those documented in this procedure. In the event of other issues, contact support@entrust.com for assistance.
Before you begin, open two browser windows, one for IDaaS and the other for Mimecast.
Step 1: Copy
the SAML Configuration 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: Copy the signing certificate from Identity as a ServiceCopy a SAML signing certificate
1. Log in to your Identity as a Service administrator account.
2. Click
> Security
> Applications. The Applications List page
appears.
3. Under SAML Cloud Integrations, click SAML Signing Certificates. The SAML Signing Certificates page appears.
4. Click
next to the certificate to copy it to the
clipboard.
You can additionally download the certificate and save it for future use.
5. Open a text editor, such as Notepad, and paste the contents of the certificate into the text file.
6. Save the file.
Step
3: Configure Mimecast for Identity as a Service authenticationConfigure Mimecast for Identity as a Service single sign-on
1. Log in to Mimecast as an administrator.
2. Go to My Apps.
3. Click Administration Console. The Administration Console Home page appears.
4. Click Services. The Services > Applications page appears.
5. Click Authentication Profiles and then click New Authentication Profile.
6. In the Description field, enter a name for the application, for example, SAML_SSO.
7. From the Allow Cloud Authentication drop-down list, select Allow Always.
8. Select Enforce SAML Authentication for End User Applications if you want Administrators to always log in to the Administration Console using an Identity Provider and then complete the following:
a. In the Issuer URL, enter the Entity ID URL that you copied in Step 1: Copy the SAML configurations from Identity as a Service.
b. Set the Identity Mapping to EMAIL.
c. In the Login URL, enter the Single Sign-ON URL that you copied in Step 1: Copy the SAML configurations from Identity as a Service.
d. In the Logout URL, enter the Single Logout URL that you copied in Step 1: Copy the SAML configurations from Identity as a Service.
e. In the Identity Provider Certificate (Metadata) field, paste the certificate you copied in Step 2: Copy the SAML signing certificate from Identity as a Service.
f. Select the Allow Single Sign On checkbox to enable Single Sign On for Administrator Users.
g. Leave the remaining settings at the default values.
9. Select Enforce SAML Authentication for Mimecast Web Apps if you want users to always log in to the Mimecast Web Apps using an Identity Provider, and then complete the following:
a. In the Issuer URL, enter the Entity ID URL that you copied in Step 1: Copy the SAML configurations from Identity as a Service.
b. Set the Identity Mapping to EMAIL.
c. In the Login URL, enter the Single Sign-ON URL that you copied in Step 1: Copy the SAML configurations from Identity as a Service.
d. In the Logout URL, enter the Single Logout URL that you copied in Step 1: Copy the SAML configurations from Identity as a Service.
e. In the Identity Provider Certificate (Metadata) field, paste the certificate you copied in Step 2: Copy the SAML signing certificate from Identity as a Service.
f. Select the Allow Single Sign On checkbox to enable Single Sign-on for Administrator users.
g. Leave the remaining settings at the default values.
10. Select Enforce SAML Authentication for End User Applications if you want users to always log in to the End User Applications using an Identity Provider, and then complete the following:
a. In the Issuer URL, enter the Entity ID URL that you copied in Step 1: Copy the SAML configurations from Identity as a Service.
b. Set the Identity Mapping to EMAIL.
c. In the Login URL, enter the Single Sign-ON URL that you copied in Step 1: Copy the SAML configurations from Identity as a Service.
d. In the Logout URL, enter the Single Logout URL that you copied in Step 1: Copy the SAML configurations from Identity as a Service.
e. In the Identity Provider Certificate (Metadata) field, paste the certificate you copied in Step 2: Copy the SAML signing certificate from Identity as a Service.
f. Select the Allow Single Sign On checkbox to enable Single Sign-on for end users.
g. Leave the remaining settings at the default values.
11. Click on Save and Exit.
12. Click Go Back to return to the Applications page.
13. Click New Application Settings. The Common Applications Settings page appears.
a. Under Description, enter a name for the profile, for example, SAML_SSO.
b. Next to Group, click Lookup and select the desired group from the list, for example, Permitted Senders. User under this group need to be present in IDaaS.
c. Next to Authentication Profile, click Lookup and select the Authentication Profile that you created in step 6 (for example, SAML_SSO).
d. Leave the remaining settings at the default values.
14. Click on Save and Exit.
Step 4: Add
Mimecast to Identity as a ServiceAdd Mimecast 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 Mimecast. The Add Mimecast 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. For the next steps, refer to https://community.mimecast.com/s/article/email-security-cloud-gateway-global-saml-urls-and-audience-values for the values required for the fields.
a. In the Default Assertion Consumer Service URL, enter the URL for your region. You can find this information in the provided link under Destination > End User Applications.
Example: If your region is the United States, you would enter https://us-api.mimecast.com/login/saml
b. In the Service Provider Entity ID field, enter the URL value for your region. You can find this information in the provided link under End User Applications.
Example: If your region is the United States, you would enter us-api.mimecast.com.<ACCOUNTCODE> where <ACCOUNTCODE> is the code assigned to your Mimecast account. You can find your account code in Mimecast by going to Administration > Account > Account Settings.
11. Enter the SAML Session Timeout to the time when the SAML Assertion times out. The maximum is 720 minutes.
12. Enter the Max Authentication Age (seconds) to set the maximum amount of time that can elapse before a user is required to reauthenticate during a new login attempt. This applies for both SP-initiated and IDP-initiated login. Set this field to -1 to disable this feature.
13. From the SAML NameID Attribute drop-down list, select Email.
14. From the SAML NameID Encoding Format drop-down list, select Email.
15. Select the SAML Signing Certificate that you copied in Step 2: Copy the SAML signing certificate from Identity as a Service.
16. Deselect Enable Go Back Button if you do not want users to be able to go back to the Mimecast login page to log in.
17. 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.
18. Add Alternate Assertion consumer Service URL(s) each for Administration Console and Mimecast Personal Portal.
● Example for the Administration Console: https://us-api.mimecast.com/login/sso/adcon
● Example for Mimecast Personal Portal: https://us-api.mimecast.com/login/sso/mpp
19. Add SAML Attributes as follows:
Add the First Name attribute:
a. Under SAML Attributes, click Add. The SAML Attributes dialog box appears.
b. In the Name field enter Email.
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 Email.
f. Click Add.
Add the Last name attribute:
a. Under SAML Attributes, click Add. The SAML Attributes dialog box appears.
b. In the Name field enter NameID.
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 Email.
f. Click Add.
20. Leave the remaining settings at the default values.
21. Click Submit.
Step 5: Create
a resource rule to protect access to MimecastCreate 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.
Step 6: Test
the integrationTest Service Provider login
1. Open a Web browser and enter the URL for your Mimecast. Click on Login. You are directed to Mimecast Login page.
2. Enter the Mimecast account email.
3. Click Next.
4. Respond to the second-factor authentication challenge. If you respond successfully, you are logged in to the Mimecast.
Test 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 the Mimecast account you want to access if you have more than one.
4. Respond to the second factor authentication challenge. If you respond successfully, you are logged in to Mimecast.