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

Solution: The statement is true

Reveal Solution Hide Solution

When you are trying to federate (via WS-FED) Office 365 with Okta:

Solution: You can try to federate multiple Office 365 custom domains into a single Okta Office 365 app instance via SWA SSO protocol

Reveal Solution Hide Solution

Once brought into Okta, LDAP roles are represented as:

Solution: Licences

Reveal Solution Hide Solution

Once brought into Okta, LDAP roles are represented as:

Solution: Groups

Reveal Solution Hide Solution

If you want to remove an attribute’s value in Okta, for example a value coming from AD that is not useful in any way, you have to:

Solution: Intentionally map a blank value to that specific attribute in the user profile

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 will always redirect to Okta and in this case only – will promt the user for re-authentication by manually entering Okta credentials

Reveal Solution Hide Solution

When does Okta bring LDAP groups into Okta?

Solution: During both LDAP import and JIT

Reveal Solution Hide Solution

In order for SAML to work, there is a need of an IDP and an SP and we know that already, but why is it so? Because:

Solution: An SP sends SAML assertions, while the IDP receives and validates them

Reveal Solution Hide Solution

Provisioning actions between cloud-based apps / on-premises apps and Okta are completed by using:

Solution: The OAuth 2.0 standard

Reveal Solution Hide Solution

As an Okta best-practice / recommendation: Okta encourages you to switch from Integrated Windows Authentication (IWA or DSSO) to agentless Desktop Single Sign-on (ADSSO). Okta is no longer adding new IWA functionality and offers only limited support and bug fixes.

Solution: Only the first statement is true

Reveal Solution Hide Solution