One Identity Safeguard for Privileged Sessions 6.0 LTS - DEPRECATED Okta Multi-Factor Authentication

Chat now with support

Get Live Help
Complete Registration

Sign In

Request Pricing

Contact Sales

Quest has tools and processes in place to identify, protect, detect, and remediate vulnerabilities and incidents when they occur, including external security partners. As part of our standard security operations, Quest does not use CrowdStrike in any of our operations. We are reviewing our third parties, and so far, there is minimal affect. It is Quest's policy not to provide further technical details unless they directly impact customer data.

One Identity Safeguard for Privileged Sessions 6.0 LTS - DEPRECATED Okta Multi-Factor Authentication - Tutorial

Table of Contents

Introduction How SPS and Okta MFA work together Technical requirements Supported factors and scenarios How SPS and Okta work together in detail Mapping SPS usernames to Okta identities Bypassing Okta authentication Configure your Okta account for SPS Configure SPS to use Okta multi-factor authentication SPS Okta plugin parameter reference

[okta] [plugin] [auth] [cache] [ldap] [username_transform] [question_1]

Store sensitive plugin data securely Perform multi-factor authentication with the SPS Okta plugin in terminal connections Perform multi-factor authentication with the SPS Okta plugin in Remote Desktop connections

whitelist

Type:	string
Required:	no
Default:	N/A

Description: The name of a user list containing gateway users configured on SPS (Policies > User Lists). You can use this option to selectively require multi-factor authentication for your users, for example, to create break-glass access for specific users.

Please select your product:

To serve you better, please complete the Purpose of your Chat:

Recommended Solutions for Your Problem

One Identity Safeguard for Privileged Sessions 6.0 LTS - DEPRECATED Okta Multi-Factor Authentication - Tutorial

whitelist