Perform the following steps to allow users to enable single sign-on (SSO) for Apex Central in Okta.
-
Integrate an on-premises Active Directory (AD).
-
In Okta, go to Directory > Directory Integrations.
-
In the Add Directory drop-down box, select Add Active Directory.
-
Click Download Agent to download the Okta AD agent.
The Agent Installation window appears.
-
Click Next to begin installing the AD agent on an on-premises AD server.
-
Select the desired organizational units (OUs) to connect to Okta, select the username format, and click Next.
We recommend selecting SAM Account Name. -
Select attributes for your user profile and click Next.
-
Click Done.
The Import Results screen appears.
-
Select users to import and click Confirm Assignments.
A confirmation message appears.
-
Click Confirm.
-
-
Configure AD user profile mappings so that you can convert Okta accounts into NETBIOS domain user account names.
-
On the user profile list, click Mappings.
The User Profile Mappings screen appears.
-
Select "samAccountName" in AD and click Save Mappings to map it to "samAccountName" in the Okta user profile.
-
Create a new application for the Apex Central instance.
-
Go to Applications > Add Application and select Trend Micro Apex One as a Service.
The application screen appears.
-
Click Add.
-
Enter the base URL and click Done.
-
Go to the Sign On tab, click View Setup Instructions and follow the configuration steps that appear to configure the settings.
-
Configure the username mapping between Okta and the application.
- Go to the Trend Micro Apex One as a Service User Profile Mappings screen.
- Select Okta to Trend Micro Apex One as a Service.
-
Define the mapping by selecting an option in the drop-down menu or by specifying an expression, and then click Save Mappings.
The format accepted by Apex Central is <domain_name>\<samaccountname>. Specify the expression that meets this specification according to your Active Directory.Examples:
- substringBefore( substringAfter(user.email, "@"), ".") + "\" + substringBefore( user.email, "@") (How to Configure SAML 2.0 for Trend Micro Apex One as a Service - Step 8)
- substringBefore( substringAfter(user.login, "@"), ".") + "\" + user.samAccountName
- "<domain_name>"+ "\" + user.samAccountName
-
Assign the application to Okta users.
-
Go to Assign > Assign to People.
The application assignment window appears.
-
Locate the user you want to assign the application to and click Assign.
If the mapping defined in step 3-e is correct, then the value of the windowsAccountName field will be <domain_name>\<samaccountname> after assigning the application to a user.
- Click Save and Go Back, and then click Done on the Assign Trend Micro Apex One as a Service to People screen to finish.
-
-
-
Integrate AD with Apex One as a Service.
For detailed instructions, refer to the KB article: Integrate Active Directory (AD) with Apex One as a Service and go to step 2 of Synchronize AD information and authenticate AD accounts.
- In Apex Central, go to Administration > Account Management > User Accounts.
-
Click Add.
-
Select Active Directory user or group, specify the User/Group name, and click Next.
The Add New User screen appears.
-
Select the desired role, configure folder options, and click Save.
- Go to Administration > Settings > Active Directory and Compliance Settings > Active Directory Settings.
-
Configuring ADFS for Apex Central.
- Select Enable Active Directory synchronization.
- Select Enable Active Directory authentication.
-
Specify the SSO service URL and Service identifier, and select the Signing certificate.
You can retrieve the necessary information from the How to Configure SAML 2.0 for Trend Micro Apex One as a Service tutorial. - Click Save.