Once brought into Okta, LDAP roles are represented as:

Solution: Email lists

Reveal Solution Hide Solution

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 valid, but Okta is not the one doing decryption – the browser is doing that

Reveal Solution Hide Solution

Regarding Access Request Workflow, when a user requests an app – he can also include a message to the approver. But you can also designate an approver group.

Solution: Only the second statement is true

Reveal Solution Hide Solution

The SCIM protocol is <response_is_entered_here> for provisioning and managing identity data on the web.

Solution: An application-level REST protocol

Reveal Solution Hide Solution

After you turn on Desktop SSO, a default DSSO related routing rule is created. You must configure the network information for this rule.

Solution: You have nothing to do and even the rule is by default set to "Active"

Reveal Solution Hide Solution

In Okta’s KB articles the set of functions under the ‘Provisioning’ concept are referred to as CRUD. This is a concept you also meet when referring to CRUD APIs .

What about its meaning here, in Okta’s vision?

Solution: In ‘Provisioning’, CRUD stands for Create, Read, Upload, Deprovision

Reveal Solution Hide Solution

Regarding Access Request Workflow, when a user requests an app – he can also include a message to the approver. But you can also designate an approver group.

Solution: Both statements are true

Reveal Solution Hide Solution

When a user’s Okta password is changed:

Solution: All apps that are Provisioning-enabled and have Update Attributes option active under Provisioning settings – will begin to sync the password in respective apps, as password is an attribute of their profile – 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

When a user signs out of Okta, if they are using IWA, they’ll be redirected to the Sign In page and without inputting credentials they’ll be signed back in

Solution: Statement is true, but then they’ll be displayed a 403 HTTP code (Forbidden)

Reveal Solution Hide Solution

When does Okta bring LDAP groups into Okta?

Solution: Only during an LDAP import

Reveal Solution Hide Solution