Configuring Okta

Views:

Configure Okta as a SAML (2.0) identity provider for Trend Vision One to use.

Okta is a standards-compliant OAuth 2.0 authorization server that provides cloud identity solutions for your organization. Okta is a single sign-on provider that allows you to manage user access to Trend Vision One.

Before you begin configuring Okta, make sure that:

You have a valid subscription with Okta that handles the sign-in process and that eventually provides the authentication credentials to the Trend Vision One management console.
You are logged on to the management console as a Trend Vision One administrator.

Procedure

Log in to your Okta organization as a user with administrative privileges.
Add a new application for Trend Vision One.
1. Click Admin in the upper right, and then navigate to Applications → Applications.
2. Click Add Application, and then click Create New App.
  
  The Create a New Application Integration screen appears.
3. Select Web as the Platform and SAML 2.0 as the Sign on method, and then click Create.
  
  The General Settings section of the Create SAML Integration screen appears.
4. On the General Settings screen, type a name for Trend Vision One in App name, for example, "Trend Vision One", and click Next.
  
  The Configure SAML section of the Create SAML Integration screen appears.
Configure SAML settings for the Trend Vision One application.
1. On the Configure SAML screen, type the Trend Vision One logon URL in Single sign on URL.
  The logon URL can be obtained from the SP metadata file downloaded from Trend Vision One.
  
  Open the SP metadata file in a text editor, and then copy the value of the Location attribute for the md:AssertionConsumerService element. Use the copied value as the logon URL.
  
  In the following example, the logon URL is https://example.com/xdr-logon-url.
```
...
    <md:AssertionConsumerService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="https://example.com/xdr-logon-url" index="0"/>
  </md:SPSSODescriptor>
</md:EntityDescriptor>
```
2. Select Use this for Recipient URL and Destination URL.
3. Specify the audience URI in Audience URI (SP Entity ID).
  The audience URI can be obtained from the SP metadata file downloaded from Trend Vision One.
  
  Open the SP metadata file in a text editor, and then copy the value of the entityID attribute for the md:EntityDescriptor element. Use the copied value as the audience URI.
  
  In the following example, the audience URI is https://example.com/xdr-audience-uri.
```
<?xml version="1.0"?>
<md:EntityDescriptor xmlns:md="urn:oasis:names:tc:SAML:2.0:metadata" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" entityID="https://example.com/xdr-audience-uri">
  <md:SPSSODescriptor protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol" AuthnRequestsSigned="true" WantAssertionsSigned="true">
...
```
4. For Name ID format, select Email Address.
5. For Application username, select Okta username.
6. Click Next.
  
  The Feedback section of the Create SAML Integration screen appears.
For Are you a customer or partner, select I'm an Okta customer adding an internal app, and then click Finish.

The Sign On tab of your newly created Trend Vision One application appears.
In the Settings table, under Sign on Methods, download and save the file for the Identity Provider metadata.

Note

Import this metadata file to Trend Vision One.
Assign the application to groups and add people to groups.
1. Select Directory → Groups.
2. Click the groups that you want to assign the application to, and then click Manage Apps.
  
  The Assign Applications screen appears.
3. Locate Trend Vision One you added and click Assign.
4. Click Manage People.
  
  The Add People to Groups screen appears.
5. Locate the user you want to allow access to Trend Vision One and add the user to the Trend Vision One group.
6. Confirm that the application is assigned to the user and group.
  
  After assigning an application to a group, the system automatically assigns the application to all users in the group.
7. Repeat the above steps to assign the application to more groups as necessary.

Procedure

Note