This is an Early AccessEarly Access (EA) features are opt-in features that you can try out in your org by asking Okta Support to enable them. Additionally, the Features page in the Okta Admin Console (Settings > Features) allows Super Admins to enable and disable some EA features themselves. feature. To enable it, use the Early Access Feature Manager as described in Manage Early Access and Beta features .
Configure streamlined Device Enrollment and Workspace ONE login using Okta
You can configure this use case to provide end usersIn Okta literature, we generally refer to "end users" as the people who have their own Okta home page (My Applications), using apps to authenticate into all of their apps. End users do not have any administrative control. When we refer to "users" we are generally referring to the individual(s) who have administrative control. a streamlined device enrollment experience, leverage Okta's extensible Multi Factor AuthenticationAuthentication is distinct from authorization, which is the process of giving individuals access to system objects based on their identity. Authentication merely ensures that the individual is who he or she claims to be, but says nothing about the access rights of the individual. Authentication methods and protocols include direct auth, delegated auth, SAML, SWA, WS-Fed, and OpenID Connect. to applications in Workspace ONE, and provide a consistent and familiar login experience for users and administrators.
This configuration is configured in VMware Identity Manager, the identity component of Workspace ONE.
To configure this use case:
|Other use case:||Enforce Device Trust and SSO for mobile devices with Okta + VMware Workspace ONE|