In an agentless DSSO (Desktop Single Sign-on) scenario Okta is the one decrypting the Kerberos ticket, finds then the user name, authenticates the user and passes back a session to the browser.

Solution: The statement is entirely valid

Reveal Solution Hide Solution

When a user’s Okta password is changed:

Solution: All apps that are Provisioning-enabled and have Sync Password option active under Provisioning settings – will begin to sync the password in respective apps, but only if JIT Provisioning is enabled as well as it has to be a just-in-time action, the moment the user resets the password

Reveal Solution Hide Solution

In an SP-initiated SAML 2.0 flow, the SP will never redirect to Okta if the session is already active

Solution: It might be seamless for the user, but the redirect is happening

Reveal Solution Hide Solution

When does Okta bring LDAP roles into Okta?

Solution: During both LDAP import and JIT

Reveal Solution Hide Solution

Any … <answer_goes_here>’s credentials verified under "Test API credentials" in an Office365 app integration can allow Okta API integration with Office 365 – permissions which once successfully granted will be used by Okta used for Provisioning related tasks

Solution: Office 365 Global Administrator

Reveal Solution Hide Solution