Splunk® Enterprise

Securing Splunk Enterprise

Configure Splunk Enterprise to use RSA Authentication Manager multifactor authentication via the REST endpoint

You can configure multifactor authentication via REST endpoints.

  • To configure multifactor authentication for Splunk Web, you use the /services/admin/Rsa-MFA endpoint. To enable CLI and management port, set the parameter enableMfaAuthRest to true.
  • To verify the authentication, you use the /services/admin/Rsa-MFA-config-verify/ endpoint.

For details, see the REST API documentation for RSA_Multifactor_Authentication_REST_API_usage_details.

Two factor authentication when connecting to REST endpoints

When multifactor authentication is turned on for the management port, the user will need to pass the passcode encoded in the basic auth header to authenticate the user. The passcode is a combination of the user's authentication PIN and the RSA-generated tokencode. For example, if the user's PIN is 1111 and RSA generates a tokencode of 2222, the passcode is 11112222.

The following command shows the user passing the passcode 11112222 to authenticate: curl -k -u user1:root_123:11112222 -X GET https://localhost:8090/services/saved/searches

You may also need to connect to the auth/login REST endpoint using the RSA tokencode to acquire a session key. For example:

curl -k https://localhost:8089/services/auth/login -d username=user1 -d password=changed -d passcode=11112222
<response>
<sessionKey>LfyRYqGEvt6aeOcotdBvqLBTDGG6Jk6HJEx56WqrhBYNrWrZRFrZ8XBgPRh4_kbrBMN4oJa2BF4dat7PjwB23Ebl6mmCYuGcXYJN4U1BJzCEviqVKKN</sessionKey>
<messages>
<msg code=""></msg>
</messages>
</response>

You cannot use the SDK to authenticate once the backend RSA multifactor authentication is enabled.

Last modified on 15 August, 2018
Configure RSA authentication from Splunk Web   Configure Splunk Enterprise to use RSA Authentication Manager multifactor authentication in the configuration file

This documentation applies to the following versions of Splunk® Enterprise: 7.2.0, 7.2.1, 7.2.2, 7.2.3, 7.2.4, 7.2.5, 7.2.6, 7.2.7, 7.2.8, 7.2.9, 7.2.10, 7.3.0, 7.3.1, 7.3.2, 7.3.3, 7.3.4, 7.3.5, 7.3.6, 7.3.7, 7.3.8, 7.3.9, 8.0.0, 8.0.1, 8.0.2, 8.0.3, 8.0.4, 8.0.5, 8.0.6, 8.0.7, 8.0.8, 8.0.9, 8.0.10, 8.1.0, 8.1.1, 8.1.2, 8.1.3, 8.1.4, 8.1.5, 8.1.6, 8.1.7, 8.1.8, 8.1.9, 8.1.10, 8.1.11, 8.1.12, 8.1.13, 8.1.14, 8.2.0, 8.2.1, 8.2.2, 8.2.3, 8.2.4, 8.2.5, 8.2.6, 8.2.7, 8.2.8, 8.2.9, 8.2.10, 8.2.11, 8.2.12, 9.0.0, 9.0.1, 9.0.2, 9.0.3, 9.0.4, 9.0.5, 9.0.6, 9.0.7, 9.0.8, 9.0.9, 9.0.10, 9.1.0, 9.1.1, 9.1.2, 9.1.3, 9.1.4, 9.1.5, 9.1.6, 9.1.7, 9.2.0, 9.2.1, 9.2.2, 9.2.3, 9.2.4, 9.3.0, 9.3.1, 9.3.2, 9.4.0


Was this topic useful?







You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters