Step
1: Copy the SAML configurations from Identity as a ServiceSiteMinder provides policy-based authentication and single sign-on for Web-based applications. See https://www.broadcom.com/products/identity/siteminder. You can protect access to SiteMinder by integrating SiteMinder with Identity as a Service. Once integrated, users can use single sign-on to log in to their SiteMinder account through Identity as a Service.
Note: This integration was tested using Identity as a Service version 5.33 and SiteMinder 12.8.x version. Other versions of SiteMinder 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. In one window, log in to your SiteMinder administrator account. In the other window, log in to your IDaaS administrator account.
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: Copy
the SAML 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.
Note: Be sure to same the file with the .cer extension, for example, SAML_certifcate.cer.
This integration uses SiteMinder Access Gateway as the local Service Provider and Entrust Identity as a Service as Remote Identity Provider with default settings. There are various combinations to configure a Federation Partnership.
This integration requires the following prerequisites:
● User Directory
● Policy Server
● Access Gateway server details to configure SAML, URLs to Servlets that Initiate Single Sign-on
See the SiteMinder documentation or contact your SiteMinder administrator to configure Federation Partnership.
To configure the prerequisites, you need to create Federation Entities and Federation Partnerships. This involves three steps:
Step
3.A: Configure Local SAML 2.0 SP Entity
1. Log in to the SiteMinder Administrator console.
2. Go to Tasks > Federation > Partnership Federation > Entities. The Entities page appears.
3. Click Create Entity. The Select Entity Type page appears.
4. In the Select Entity Type page, do the following:
a. For the Entity Location, select Local.
b. From the New Entity Type drop-down list, select SAML2 SP.
5. Click Next. the Configure Entity page appears.
6. In the Configure Entity page, do the following:
a. In the Entity ID field, enter the Entity ID that belongs to the remote partner.
Example: https://siteminderaccessgateway.domain.com
b. Enter an Entity Name.
c. In the Description field, enter a description for the Entity.
d. In the Base URL field enter the base location of the server that is visible to the intended users of the federation. This server is typically the server where SiteMinder is installed.
Example: https://siteminderaccessgateway.domain.com
Note: Do not put a forward slash at the end of the base URL. A final slash results in two slashes being appended to other URLs that use this base URL.
e. Expand the Supported Name ID Formats and select Unspecified.
f. Leave the remaining settings at the default values.
7. Click Next. The Confirm page appears.
8. Open a text editor, such as Notepad and under Confirm, copy the following to the text file:
● Assertion Consumer Service URL
● Entity ID
You need these values in Step 4: Add SiteMinder to Identity as a Service.
9. Click Finish.
Step
3.B: Configure Remote SAML 2.0 IDP Entity
1. Log in to the SiteMinder Administrator console.
2. Go to Tasks > Federation > Partnership Federation > Entities. The Entities page appears.
3. Click Create Entity. The Select Entity Type page appears.
4. In the Select Entity Type page, do the following:
a. For the Entity Location, select Remote.
b. From the New Entity Type drop-down list, select SAML2 IDP.
5. Click Next. the Configure Entity page appears.
6. In the Configure Entity page, do the following:
a. In the Entity ID field, enter the Entity ID you copied in Step 1: Copy the SAML configurations from Identity as a Service.
b. In the Description field, enter a description for the Entity.
7. In the Remote SSO Service URLs, section, do the following:
a. From the Binding drop-down list, select HTTP-Redirect.
b. In the URL field, enter the Single Sign-on URL you copied in Step 1: Copy the SAML configurations from Identity as a Service.
8. Expand the Signature and Encryption options section and do the following:
a. Click Import. The Select File page appears.
b. For the Input File As, select Single Key / Cert File.
c. Click Browse and browse to select the SAML signing certificate you file downloaded in Step 2: Copy the SAML signing certificate from identity as a Service.
9. Click Next. The Confirm page appears.
10. Click Finish.
Step
3.C: Configure Partnerships
1. Log in to the SiteMinder Administrator console.
2. Go to Tasks > Federation > Partnership Federation > Partnerships. The Partnerships page appears.
3. Click Create Partnership.
4. From the Create Partnership drop-down list, select SAML2 SP -> IDP. The Configure Partnership page appears.
5. In the Configure Partnership page, do the following:
a. Enter a Partnership Name. For example, EntrustIDaaSSiteminderPartnership.
b. From the Local SP list, select the Entity you created in Step 3.A: Configure Local SAML 2.0 SP Entity.
c. From the Remote IDP list, select the Remote SAML 2.0 IDP Entity you created in Step 3.B: Configure Remote SAML 2.0 IDP Entity.
d. Set the Skew Time (Seconds) to 30.
e. Under User Directories and Search order, select the user directory configured for the SiteMinder Policy Server and move it to Selected Directories.
6. Click Next. The User Identification page appears.
7. In the User Identification page, do the following:
a. Select Use Name ID.
b. From the NameIDPolicy Format drop-down list, select *Unspecified.
c. In the LDAP Search Specification. field enter the LDAP search specification. This value changes depending on the LDAP used. For example, for ODSEE LDAP, the value is uid=%s.
d. For Federated Users, under User Class, select All Users in Directory.
e. Leave the remaining settings at the default values.
8. Click Next. The SSO and SLO page appears.
9. In the SSO and SLO page, do the following:
a. For the Authentication Binding Request, select HTTP-Redirect.
b. For the SSO Profile, select HTTP-POST.
c. From the Issuer Format drop-down list, select *Unspecified.
10. Click Next. The Configure AuthnContext page appears.
11. Leave the Configure AuthnContext settings at the defaults.
12. Click Next. The Signature and Encryption page appears.
13. In the Signature and Encryption page, do the following:
a. From the Verification Certificate Alias: drop-down list, select the certificate you imported in Step 3.B: Configure Remote SAML2.0 IDP Entity.
b. Leave the remaining settings at the default values.
14. Click Next. The Application Integration page appears.
15. In the Application Integration page, do the following:
a. Redirect Mode : No data, default setting
b. In the Target field, enter the URL that is protected by SAML. This is the resource protected behind the SiteMinder Access Gateway.
16. Leave the remaining settings at the default values.
17. Click Next. The Confirm page appears.
18. Review all settings and then click Confirm.
Step 4: Add
SiteMinder to Identity as a Service1. In Identity as a Service, click
> Security > Applications.
The Applications Lists
page appears.
2. Click Add. The Select an Application Template page appears.
3. Under SAML Cloud Integrations, click SiteMinder. The Add SiteMinder page appears.
4. Enter an Application Name.
5. Enter an Application Description.
6. 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.
7. Select the Authentication Flow that appears to users during login.
8. Click Next. The General page appears.
9. In the Default Assertion Consumer URL field, enter the Assertion Consumer Service URL, enter the Assertion Consumer URL you copied from SiteMinder in Step 3.B: Configure Remote SAML IDP Entity.
10. In the Service Provider Entity ID field, enter:
11. In the Single Logout Service URL field, enter the Single Sign-on URL you copied from SiteMinder in Step 3.B: Configure Remote SAML IDP Entity.
12. Enter the SAML Session Timeout to the time when the SAML Assertion times out. The maximum is 720 minutes.
13. 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.
14. From the SAML NameID Attribute drop-down list, select User ID.
15. From the SAML NameID Encoding Format drop-down list, select Unspecified.
16. From the SAML Signing Certificate from the drop-down list, select the SAML Signing Certificate that you imported into SiteMinder.
17. Deselect Enable Go Back Button if you do not want users to be able to go back to the ReviewInc 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. Add an Alternate Assertion Consumer Service URL
a. Click Add.
b. Enter a Name.
c. Enter a URL Value field. For example, https://<userID>.<mycompany.com>/SAML20/
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.
20. Leave the remaining settings at the default values.
21. Click Submit.
Step 5: Create
a resource rule to protect access to SiteMinderCreate 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 integrationTesting Service Provider Login
See the Siteminder documentation regarding URLs to Servlets that Initiate Single Sign-on.
Note the following:
● The page with these hard-coded links must reside in an unprotected realm.
● The hard-coded link that the user selects must contain specific query parameters, which are used in an HTTP GET request to the AuthnRequest service.
The syntax for the link is:
Example: http://sp_server:port/affwebservices/public/saml2authnrequest?ProviderID=idp_id&RelayState=target_URL
https://cag.domain.com/affwebservices/public/saml2authnrequest?ProviderID=https://entrust.us.trustedauth.com/api/saml&RelayState=https://cag.domain.com/saml
To test Service Provider login
1. Access the hard-coded link to be redirected to the Identity as a Service login page.
2. Log in with your first factor credentials.
3. Respond to the second-factor authentication challenge. If you respond successfully, you are redirected Target URL of SiteMinder.
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 SiteMinder.
4. Respond to the second-factor authentication challenge. If you respond successfully, you are logged in to SiteMinder.