Adding and configuring the Centrify Browser Extension (advanced) application in the Admin Portal
To add and configure a Browser Extension (advanced) application:
- In the Admin Portal, click Apps > Web Apps. Click Add Web Apps. The Add Web Apps screen appears.
- Click Custom. On the Custom tab, next to the Browser Extension (advanced)application, click Add.
- On the Add Web App screen, click Yes to add the application. The Admin Portal adds the application.
- Click Close to exit the Application Catalog.
- On the Web Apps page, choose the Browser Extension (advanced) app you just added.
- On the Description page, select if you'd like custom name and description for each language. Additonally, add the name, description, category, and logo for the application. For some applications, the name cannot be modified.
- Because this is a generic or custom application, it’s recommended to give this application a unique name.
- On the Permissions page, select the role(s), groups, and/or users that have access to the application.
- (Optional) On the Policy page, specify additional authentication controls for this application. Here, you can add rules.
- Click Add Rule. The Authentication Rule window displays.
- Click Add Filter on the Authentication Rule window.
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:
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.
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.
The authentication factor is a date before or after which the user logs in that triggers the specified authentication requirement.
The authentication factor is a specific date range.
The authentication factor is a specific time range in hours and minutes.
The authentication factor is the device operating system.
The authentication factor is the browser used for opening the Centrify PAS.
The authentication factor is the country based on the IP address of the user computer.
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.
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.
- Click the Add button associated with the filter and condition.
- 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.
- Click OK.
- (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.
- Click Save.
- 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.
On the Account Mapping page, configure how the login information is mapped to the application’s user accounts.
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.
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.
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
loginData.addField("username", "input#username1", LoginUsername);
loginData.addField("password", "input#password1", LoginPassword);
- (Optional) Click App Gateway to allow users to securely access this application outside of your corporate network. For detailed configuration instructions, see Configuring an application to use the App Gateway.
- (Optional) On the Changelog page, you can see recent changes that have been made to the application settings, by date, user, and the type of change that was made.
- (Optional) Click Workflow to set up a request and approval work flow for this application. See Configuring a request and approval workflow for more information.
- Click Save.