After the future removal of the classic playbook editor, your existing classic playbooks will continue to run, However, you will no longer be able to visualize or modify existing classic playbooks.
For details, see:
Secure using two factor authentication
Duo is integrated with to enable two factor authentication. When enabled, two factor authentication applies to all local users. sets each user's email address as the Duo username. If an email address is not available, then the username is used.
Perform the following steps to enable two factor authentication in :
- Create a web SDK application in the Duo administrative interface. Refer to your Duo documentation for more information.
- When the web SDK application integration is ready, record the following information to provide to :
- Integration key
- Secret key
- API hostname
- In , from the Home menu, select Administration.
- Select User Management > Two Factor.
- Check the Enable Duo Two Factor Authentication checkbox.
- Provide the information you collected in the Integration Key, Secret Key, and API Hostname fields.
- Click Test Duo Connectivity to verify the keys and hostname are correct.
- Click Save Changes.
Disable two factor authentication for the default admin account as a failsafe mechanism so there is at least one account that can log in to administer Duo settings if the integration breaks.
With two factor authentication enabled, two new fields appear in the Edit User page:
- Two Factor Authentication. Set this field to Duo to enable two factor authentication. Select None to disable two factor authentication.
- Duo Username. Use this field to make sure the and Duo usernames match. For example, a user's username is jsmith but his Duo username is jsmith@splunk.com. In this case, set the Duo username to jsmith@splunk.com so the correct Duo user is used when logging in to .
Configure single sign-on authentication for | Configure role based access control inside Splunk apps |
This documentation applies to the following versions of Splunk® SOAR (On-premises): 5.1.0, 5.2.1, 5.3.1, 5.3.2
Feedback submitted, thanks!