Signing in to QTDMP with Okta (BYOI)

Signing in with your organization’s Okta account is available once a Quest administrator configures Okta as a federated identity provider for QTDMP. QTDMP uses Microsoft Entra External ID as its CIAM (Customer Identity and Access Management) tenant for external customer identities. During sign-in, Entra External ID redirects users to your organization’s Okta instance for authentication, then returns a trusted token to QTDMP. Your organization continues to enforce its own Okta sign-in policies, including conditional access and multi-factor authentication.

QTDMP does not receive or store users’ Okta passwords. The access token used by QTDMP has a 10-minute lifetime, is refreshed automatically while the user is active, and expires after inactivity, at which point the user must sign in again.

Onboarding /Configuration Steps

Enabling Okta sign-in requires a one-time exchange of configuration values between your Okta administrator and a Quest representative, over an agreed secure channel. See SAML Setup Procedure for additional details.

NOTE: Before users can sign in with their organization’s Okta account, the following one-time setup must be completed:

  1. An administrator sets up the Okta integration for the organization using the configuration details provided by Quest.
  2. The required integration details are shared with Quest using an approved secure channel.
  3. Quest configures the organization’s federation in the shared Microsoft Entra External ID (CIAM) tenant.

To sign in with Okta-based access

  1. Open the QTDMP sign-in page.
  2. Enter your work email address on the pre-authentication page. (QTDMP uses the email domain to route the user to the correct Okta instance.)
  3. Authenticate with your Okta credentials.
  4. On the first sign-in, a federated user account is created in Entra External ID using minimal user information and linked to the QTDMP.
  5. On later sign-ins, the federated account is used automatically.