Scribd
Upload
17 views2 pages

Agentless DSSO Configuration in Okta

Okta provides Single Sign-On (SSO) for seamless authentication across various app integrations, allowing users to access multiple applications without reentering credentials. It supports both cloud-based and on-premises applications using protocols like SAML and OIDC, and also offers mobile app integration. Additionally, Desktop Single Sign-On (DSSO) enables automatic authentication for users on Windows networks, enhancing user experience by requiring only a single sign-in.

Uploaded by

rajkumar
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
17 views2 pages

Agentless DSSO Configuration in Okta

Okta provides Single Sign-On (SSO) for seamless authentication across various app integrations, allowing users to access multiple applications without reentering credentials. It supports both cloud-based and on-premises applications using protocols like SAML and OIDC, and also offers mobile app integration. Additionally, Desktop Single Sign-On (DSSO) enables automatic authentication for users on Windows networks, enhancing user experience by requiring only a single sign-in.

Uploaded by

rajkumar
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

Single Sign-On

The Okta app integrations in your org use Single Sign-On (SSO) to provide a
seamless authentication experience for end users. After end users sign in to
Okta, they can launch any of their assigned app integrations to access
external apps and services without reentering their credentials. For apps that
support federated SSO through SAML, OIDC, or any other proprietary
authentication protocol, Okta establishes a secure connection with a user's
browser and then authenticates the user. With SSO, a central domain
performs authentication and then shares the session with other domains. The
way a session is shared may differ between the various SSO protocols, but
the general concept is the same.
Okta provides SSO access to thousands of supported cloud-based apps
through the Okta Integration Network (OIN). The integrations in the OIN can
use OpenID Connect (OIDC), SAML, SWA, or proprietary APIs for SSO. Okta
maintains the SSO protocols and provisioning APIs.
Okta also provides integrations for SSO to on-premises web-based apps. You
can integrate on-premises apps using SWA or SAML toolkits. Okta also
supports provisioning and deprovisioning users with apps that expose their
provisioning APIs publicly.
Okta provides SSO integration with mobile apps whether they're iOS or
Android apps, or web apps optimized for mobile devices. Users can access
web app integration in the OIN using SSO from any mobile device. Mobile
web apps can use industry-standard OIDC, SAML, or Okta SWA technology.
For example, Okta can integrate with platform-specific apps like Box Mobile
using SAML authentication for registration and OAuth for ongoing usage.

Related topics
Active Directory Desktop Single Sign-on
Configure agentless Desktop Single Sign-on

Active Directory Desktop Single Sign-


on
With Desktop Single Sign-on (DSSO), your users are automatically
authenticated by Okta when they sign in to your Windows network. Following
authentication, users can access applications through Okta without entering
additional usernames or passwords. DSSO improves the user experience
because users only need to sign in a single time and don't need separate
credentials for each application they access through Okta.
Two methodologies are available for DSSO implementation:
 agentless (recommended)
 IWA web agent running on premises
If you set up registry keys for Agentless SSO, see Migrate your agentless
Desktop Single Sign-on configuration.

TopicConfigure agentless Desktop


Single Sign-on
With agentless Desktop Single Sign-on (DSSO), you don't need to deploy IWA
agents in your Active Directory domains to implement DSSO functionality.
This reduces or eliminates the maintenance overhead and provides high
availability as Okta assumes responsibility for Kerberos validation.

Topics

You might also like