Adding and configuring the Centrify Browser Extension (advanced) application in the Admin Portal

1. Click Add Rule. The Authentication Rule window displays.

1. Click Add Filter on the Authentication Rule window.

1. Define the filter and condition using the drop-down boxes. For example, you can create a rule that requires a specific authentication method when users access the Centrify Privilege Access Service from an IP address that is outside of your corporate IP range. Supported filters are:

   Filter	Description
   IP Address	The authentication factor is the computer’s IP address when the user logs in. This option requires that you have configured the IP address range in Settings, Network, Corporate IP Range.
   Identity Cookie	The authentication factor is the cookie that is embedded in the current browser by the Centrify PAS after the user has successfully logged in.
   Day of Week	The authentication factor is the specific days of the week (Sunday through Saturday) when the user logs in.
   Date	The authentication factor is a date before or after which the user logs in that triggers the specified authentication requirement.
   Date Range	The authentication factor is a specific date range.
   Time Range	The authentication factor is a specific time range in hours and minutes.
   Device OS	The authentication factor is the device operating system.
   Browser	The authentication factor is the browser used for opening the Centrify PAS.
   Country	The authentication factor is the country based on the IP address of the user computer.
   Risk Level	The authentication factor is the risk level of the user logging on to user portal. For example, a user attempting to log in to Centrify PAS from an unfamiliar location can be prompted to enter a password and text message (SMS) confirmation code because the external firewall condition correlates with a medium risk level. This Risk Level filter, requires additional licenses. If you do not see this filter, contact Centrify PAS support. The supported risk levels are: Non Detected -- No abnormal activities are detected. Low -- Some aspects of the requested identity activity are abnormal. Remediation action or simple warning notification can be raised depending on the policy setup. Medium -- Many aspects of the requested identity activity are abnormal. Remediation action or simple warning notification can be raised depending on the policy setup. High -- Strong indicators that the requested identity activity is anomaly and the user's identity has been compromised. Immediate remediation action, such as MFA, should be enforced. Unknown -- Not enough user behavior activities (frequency of system use by the user and length of time user has been in the system) have been collected.
   Managed Devices	The authentication factor is the designation of the device as “managed” or not. A device is considered “managed” if it is managed by Centrify PAS, or if it has a trusted certificate authority (CA has been uploaded to tenant).
   For the Day/Date/Time related conditions, you can choose between the user’s local time and Universal Time Coordinated (UTC) time.

1. Click the Add button associated with the filter and condition.
2. Select the profile you want applied if all filters/conditions are met in the Authentication Profile drop-down.
   The authentication profile is where you define the authentication methods. If you have not created the necessary authentication profile, select the Add New Profile option. See Creating authentication profiles.
3. Click OK.
4. (Optional) In the Default Profile (used if no conditions matched) drop-down, you can select a default profile to be applied if a user does not match any of the configured conditions.
   If you have no authentication rules configured and you select Not Allowed in the Default Profile dropdown, users will not be able to log in to the service.
5. Click Save.
   If you have more than one authentication rule, you can prioritize them on the Policy page. You can also include JavaScript code to identify specific circumstances when you want to block an application or you want to require additional authentication methods. For details, see Application access policies with JavaScript.
6. If you left the Apps section of Admin Portal to specify additional authentication control, you will need to return to the Apps section before continuing by clicking Apps at the top of the page in Admin Portal.

Use the following Directory Service field to supply the user name: Use this option if the user accounts are based on user attributes. For example, specify an Active Directory field such as mail or userPrincipalName or a similar field from Centrify Directory.

For Web - User Password applications, selecting this option allows an additional option to let Active Directory users log in using Active Directory credentials. Select the Use the login password supplied by the user (Active Directory users only) option for every Web - User Password application that you want users to log in to using Active Directory credentials.

Everybody shares a single user name: Use this option if you want to share access to an account but not share the user name and password. For example, some people share an application developer account.

Prompt the user for their user name: Use this option if you want users to supply their own user name and password. The first time a user launches the application, they enter their login credentials for that application. The Centrify PAS stores the user name and password and the next time the user launches the application, the Centrify PAS logs the user in automatically.

Use Account Mapping Script: You can customize the user account mapping here by supplying a custom JavaScript script. For example, you could use the following line as a script:

LoginUser.Username = LoginUser.Get('mail')+'.ad';

The above script instructs the Centrify PAS to set the login user name to the user’s mail attribute value in Active Directory and add ‘.ad’ to the end. So, if the user’s mail attribute value is Adele.Darwin@acme.com then the Centrify PAS uses Adele.Darwin@acme.com.ad. For more information about writing a script to map user accounts, see the User-password application scripting.

On the Advanced tab, click Edit to enter or modify the JavaScript that specifies the login data that the Centrify PAS sends to the web application login URL when a user requests the application. This advanced script must be present and configured to match the service provider’s required form fields.

The default example script shows how to specify form fields. The example script does not work as is, and you must modify the script to match th requirements of each application. For the vast majority of web applications, you need to replace only the following:

• "<url>" (line 1) = Replace with the application URL.

• "<username selector>" (line 2) = Replace this with the application selector object for name.

• "<password selector>" (line 3) = Replace this with the application selector object for password.

• "<submit selector>" (line 4) = Replace this with the application selector object for submit.

• "<form selector>" (line 5) = Replace this with the application selector object for form.

The following is an example using username and password:

loginData.addField("username", "input#username1", LoginUsername);

loginData.addField("password", "input#password1", LoginPassword);