Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Add JIMS Configuration

Use the Add JIMS Configuration page to configure a JIMS profile to obtain user identities. Ensure that you have added the IP address of Security Director Insights in the JIMS server.

To add a JIMS configuration:

  1. Select Administration> Insights Management> Identity Settings.

    The Identity Settings page appears.

  2. Click Create.

    The Add JIMS Configuration page appears.

  3. Complete the configuration according to the guidelines provided in Table 1.
  4. Click Save.

    A new JIMS configuration is added to Security Director Insights and listed on the Identity Settings page.

Table 1: Add JIMS Configuration

Setting

Guideline

JIMS Endpoint Hostname/IP

Enter a valid IPv4 or IPv6 address or the hostname of the JIMS server.

JIMS Port Number

Select the connection port of the JIMS server from the list. The range is 1 to 65,535.

SSL

Select an SSL setting: Enabled or Disabled.

Identity Sources

Select an identity source to collect data from: Active Directory, Syslog, or both.

Use Reverse DNS

Reverse DNS lookup converts an IP address to hostname to identify the domain name of the source. Choose to enable or disable the Use Reverse DNS setting. This option is enabled by default.

Exclude hostnames

You can disallow identity mapping for certain hosts. Enter the hostnames separated by commas. Identity mappings for these hosts are ignored and not included in event handling and displays.

OAuth Client ID

Enter the Open Authorization (OAuth) client ID that the Security Director Insights provides to the JIMS server as part of its authentication. Security Director Insights must authenticate itself with the JIMS server to obtain an access token that allows it to query the JIMS server for user identity information.

The client ID must be consistent with the API client configured on JIMS.

OAuth Client Secret

Enter the client secret that Security Director Insights provides to the JIMS server as part of its authentication. The client secret must be consistent with the API client configured on JIMS.

Related Documentation