Step 1: Create
and map a custom user attribute for ADPADP is a cloud-based management solution for human resources, such as payroll, benefits, and tax management (see https://www.adp.com/). You can configure your ADP account for Single Sign-On (SSO) through Identity as a Service.
Note: This guide was tested using previous versions of Identity as a Service and ADP. Other versions of ADP may require integration and configuration steps that differ from those documented in this procedure. For newer versions of ADP, this integration guide may be used as an initial approach for integrating ADP. In the event of other issues, contact support@entrust.com for assistance.
Before you begin, add a PersonImmutableID attribute in Active Directory.
Step 1: Create
and map a custom user attribute for ADPCreate custom user attributes in Identity as a Service
You need to create custom user attribute to fully integrate ADP.
1. Create a custom PersonImmutableID attribute as follows:
a. Click 
> Members > Attributes.
The User Attributes List page appears.
b. Under Custom User Attributes, click Add. The Add User Attribute dialog box appears.
c. Enter PersonImmutableID for the User Attribute Name.
d. Select Attribute is required to make the user attribute mandatory.
e. Click Add.
2. Map the ADP employeeID/ADP WFN Associate ID to the PersonImmutableID attribute, as follows:
a. Click
> Directories. The Directories
List page appears.
b. Click the directory name. The Edit Directory page appears.
c. Scroll to the Custom User Attributes and locate PersonImmutableID.
d. Enter PersonImmutableID in the field to map to the PersonImmutableID attribute.
e. Click Save.
f. Click 
to the right of the directory to synchronize it with your Active Directory.
3. Ensure that the ADP generated Employee ID/Associate ID is present and it is populated for all users.
a. Click
> Users.
The Users List page appears.
b. Select a user and scroll to the PersonImmutableID user attribute and confirm that the field has been populated.
Note: ADP requires PersonImmutableID to recognize your employee in your organization's authentication server. Your organization should not reuse this value to associate it with other employees. PersonImmutableID is a unique value between 1 and 100 characters in length and includes English letters and numbers.
Step 2: Add
ADP to Identity as a ServiceAdd ADP 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 ADP. The Add ADP 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. If available, use the Upload Metadata XML file option to auto-populate the following fields, if available in the file:
● Default Assertion Consumer Service URL
● Alternative Assertion Consumer URLs
● Service Provider Entity ID (Issuer)
● Single Logout Service URL
● SAML Signing Certificate
● SAML NameID Encoding Format
● SAML Signature Algorithm
11. To import the Metadata file:
a. Click and browse
to select the file. The Metadata
Configuration dialog box appears.
b. If required, click Merge with existing values to merge new values with existing values for Alternative Assertion Consumer Services URLs and SAML attribute names.
c. Click Save.
12. If you do not have a metadata file, enter the following:
a. Enter the Default Assertion Consumer Service URL for the SAML application.
b. Enter the Service Provider Entity ID (Issuer) that is used by Identity as a Service to identify the SAML service provider.
c. If your SAML service provider supports SAML logout, set the Single Logout Service URL to the value supplied by your SAML service provider. Otherwise, leave it blank.
d. Optional. Enter the SAML Username Parameter Name used to identify 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 identity the IDaaS userID
e. 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.
f. Enter the SAML Session Timeout to the time when the SAML Assertion times out. The maximum is 720 minutes.
g. 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.
h. From the SAML Name ID Attribute drop-down list, select User ID.
i. From the SAML NameID Encoding Format, select UNSPECIFIED.
j. From the SAML Response Signature Algorithm, selectSHA256.
k. Select the SAML Signing Certificate from the drop-down list.
13. Select Sign complete SAML response to ensure the message integrity of the SAML response sent to the application during authentication.
14. Optional: Select Respond Immediately for Unsuccessful Responses to return to the application immediately after a login failure, rather than allow user to try again with a different userID.
15. Deselect Enable Go Back Button if you do not want users to be able to go back to the ADP login page to log in.
16. 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.
17. 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.
18. Under SAML Attribute(s), do the following:
a. Click Add.
b. In the Name field, enter PersonImmutableID.
c. From the drop-down list, select the Name Format for the attribute.
d. Click Add in the Value(s) field, type < and select the PersonImmutableID attribute.
e. Click Edit.
19. Click Submit.
Step 3: Create
a resource rule to protect access to ADPLimitation: Resource rules for SAML applications cannot have resource rules with External Authentication set as the First Authentication Step.
Create 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. 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.
8. 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.
Note: Identity as a Service uses GeoLite2 data created by MaxMind, available from http://www.maxmind.com.
9. Click Source IP Address to set the IP Context Condition Settings, as follows:
a. Click Add to add the IP Addresses that you want to allow or block.
b. Enter the IP Address/CIDR that you want to allow or block.
c. Click the icon to toggle between 
Allow
and 
Block.
d. Repeat steps a-c until all the required IP addresses/CIDR are added to the list.
e. Click Save to return to the Authentication Conditions Settings page.
10. 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 Manage machine authenticator settings.
b. Click Save.
11. 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.
12. Set the risk score for application conditions by clicking the dot next to the condition setting and sliding the risk scale to the risk percentage a user receives if they fail to meet the condition. The default setting is 0%. The Risk percentage determines the authentication requirements as set by the Authentication Decisions. When a user attempts to authenticate to an application, the final risk percentage is the sum of all failed conditions.
13. Set the risk threshold 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.
14. Set the Authentication Decisions for low, medium, and high risk, as follows:
a. Select the first-factor from the drop-down list.
The type of authenticator selected is the first type of authentication challenge a user must complete to access the application. The list of Second Factors authenticators available updates based on the type of first-factor authenticator selected.
b. Click the check boxes to select the Second Factors.
The authenticators you select are those that can be used to complete the authentication challenge.
c. Click and drag the Second Factors authenticators for the risk level so that they are ordered from top to bottom in order of preference.
d. Repeat step c for Medium Risk and High Risk.
Note: You cannot add second factors to medium and high risk if you select Deny Access is selected as the first-factor.
15. Enable Smart Login. Smart Login is available only if your account has been enabled to allow Smart Login. Smart Login can be used to authenticate to the Identity as a Service Admin Portal, User Portal, OIDC, and SAML applications integrated with Identity as a Service. See Protect applications with a resource rule for more information.
a. Select Enable Smart Login.
When you enable Smart Login, first-factor and second-factor Authenticators are used for fallback authentication.
b. Select the first-factor authentication method used for fallback.
Entrust recommends using Skip Password for first-factor. If you do not want to enable fallback authentication, select Deny Access from the first-factor drop-down list.
c. Click the check boxes to select the Second Factors used for Fallback authentication.
Entrust recommends selecting Mobile Smart Credential Push as the second factor fallback authentication method. The authenticators you select are those that can be used to complete the authentication challenge.
d. Click and drag the Second Factors authenticators for the risk level so that they are ordered from top to bottom in order of preference.
e. Repeat these steps for Medium Risk and High Risk.
Note: You cannot add second factors to medium and high risk if you select Deny Access as the first-factor.
16. Optional: Select Disable Single Sign-On for Application to force a user to re-authenticate using the authenticator level required when the user accesses the application.
Note: This setting is only available for resource rules that protect Identity as a Service Administrator and User Portals and SAML applications.
17. Optional: Click Show KBA Advanced Settings to modify the Q&A challenge size and Number of Wrong Answers Allowed for the resource rule. This setting is visible only if you select KBA for second-factor authentication and you have modified the Identity as a Service default settings for Knowledge-based authentication (see Modify knowledge-based authentication settings).
18. Click Submit to create your resource rule.
Step 4: Download
the Metadata file from Identity as a ServiceDownload the Metadata file from Identity as a Service
1. In Identity as a Service, click
> Security > Applications.
The Applications List page appears.
2. Do one of the following:
● Click
next to the application you are integrating
with Identity as a Service.
–or–
● Click
next to the application you are integrating
with Identity as a Service and select SAML IDP Metadata.
The SAML Application Metadata dialog box appears.
3. Select the certificate to include in the SAML IDP Metadata file from the drop-down list.
4. If applicable, Select the domain to include in the SAML IDP Metadata file from the drop-down list.
5. Enter the Lifetime, in days, for the SAML IDP Metadata file. The value must be between 2 and 730.
6. Do one of the following, as required:
a. Copy the Public Endpoint to paste into your SAML application being used Identity Provider authentication.
b. Click Download.
Note: If you are using multiple domains, you must download each domain's metadata file separately because the values in the metadata file vary for each domain.
Step 5: Configure
ADP for Identity as a Service single sign-onConfigure ADP for Identity as a Service single sign-on
1. Log in to your ADP account as an administrator.
2. From the Federation Setup menu, select Identity Provider.
3. From the Web Setup menu, select Services Selection, check applicable service(s) for connection, click Next
4. From Configure, read through the step by step up instructions, and then click Next.
5. Under Upload Metadata, browse to select the metadata file you downloaded in Step 4: Download the metadata from Identity as a Service. Click Upload
6. The Federated Issuer Key auto-populates.
7. Click Next.
8. Under Provision User(s), upload the unique identifier using a .csv file or Use employee ID/WFN Associate ID as the Person Immutable ID.
Testing Service Provider Login
1. Open a Web browser and enter the URL for your ADP account. You are directed to Identity as a Service.
2. Enter your ADP account User ID and click Next.
3. Respond to the second-factor authentication challenge. If you respond successfully, you are logged in to the ADP 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 ADP.
4. Respond to the second-factor authentication challenge. If you respond successfully, you are logged in to ADP.