Okta Okta-Certified-Administrator - Okta Certified Administrator Exam

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

Okta has a json representation of objects such as 'users', json schema interchanged on API calls, as an example, but what about the format of information regarding of a user going to a SCIM server for creating the user in an On Premises application?

Solution: Format stays the same: json

Does Okta require an Agent to sit in-between Okta to SCIM-enabled app on premises requests?

Solution: Yes, an Okta Provisioning Agent

What does SCIM stand for?

Solution: System of Cross-scripting-domain Identity Management

When using Okta Expression Language, which variable type results out of this Okta Expression? isMemberOfGroup("groupId")

Solution: Graph

Can you map the Okta user ID as an Office 365 Immutable ID?

Solution: Not possible and not intended to be possible as it cannot work like this

Does Okta require an Agent to sit in-between Okta to SCIM-enabled app on premises requests?

Solution: Yes, and AD Agent

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

Solution: An application-level REST protocol

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 IDP authorizes the users, while the SP authenticates them

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