Configure remote authentication through SAML

Enable SAML remote authentication

1. Log in to the Administration settings on the ExtraHop system through https://<extrahop-hostname-or-IP-address>/admin.
2. In the Access Settings section, click Remote Authentication.
3. Select SAML from the remote authentication method drop-down list and then click Continue.

• Click View SP Metadata to view the Assertion Consumer Service (ACS) URL and Entity ID of the ExtraHop system. These strings are required by your identity provider to configure SSO authentication. You can also download a complete XML metadata file that you can import into your identity provider configuration.

  Note:

  The ACS URL includes the hostname configured in Network Settings. If the ACS URL contains an unreachable hostname, such as the default system hostname extrahop, you must edit the URL when adding the ACS URL to your identity provider and specify the fully qualified domain name (FQDN) of the ExtraHop system.

• Click Add Identity Provider to add the following information:

  Provider Name: Type a name to identify your specific identity provider. This name appears on the ExtraHop system log in page after the Log in with text.

  Entity ID: Paste the entity ID provided by your identity provider into this field.

  SSO URL: Paste the single sign-on URL provided by your identity provider into this field.

  Signing Certificate: Paste the X.509 certificate provided by your identity provider into this field.

  Auto-provision users: When this option is selected, ExtraHop user accounts are automatically created when the user logs in through the identity provider. To manually control which users can log in, clear this checkbox and manually configure new remote users through the ExtraHop Administration settings or REST API. Any manually-created remote username should match the username configured on the identity provider.

  Enable this identity provider: This option is selected by default and allows users to log in to the ExtraHop system. To prevent users from logging in through this identity provider, clear the checkbox.

  User Privilege Attributes: You must configure the following set of user attributes before users can log in to the ExtraHop system through an identity provider. Values are user-definable; however, they must match the attribute names that are included in the SAML response from your identity provider. Values are not case sensitive and can include spaces. For more information about privilege levels, see Users and user groups.

  Important:

  You must specify the attribute name and configure at least one attribute value other than No access to enable users to log in.

  In the example below, the Attribute Name field is the group attribute configured when creating the ExtraHop application on the identity provider and the attribute value is the name of one of your user groups. If a user is a member of more than one group, the user is granted the most permissive access privilege.
  
  

  Packets and Session Key Access: Configuring packets and session key attributes is optional and only required when you have a connected Trace appliance.
  
  

  Detections Access: Configuring detections attributes is optional and only required when the global privilege policy is set to Only specified users can view detections. Users with unlimited or cloud setup (Reveal(x) 360) privileges are automatically granted access to detections.
  
  

User attribute mapping

You must configure the following set of user attributes in the application attribute mapping section on your identity provider. These attributes identify the user throughout the ExtraHop system. Refer to your identity provider documentation for the correct property names when mapping attributes.