When does Okta bring LDAP roles into Okta?
Solution: Only during an LDAP import
What does SCIM stand for?
Solution: System for Cross-domain Identity Management
There might be specific AD attributes, which - apart from others - do not appear in the Okta user profile. Can those extra attributes be mapped and provisioned towards an app?
Solution: Yes, but you need to have a SAML 2.0 integrated app or such flow
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 partially true, as the networking information is already added within this rule
As an Okta admin, when you implement IWA, you have to know how to successfully test it to see if it's working. For this you:
Solution: Restart AD Domain Controller and go into IIS and see if you have IWA references in there
What does SCIM stand for?
Solution: System for CRSF-domain Identity Management
Does Okta require an Agent to sit in-between Okta to SCIM-enabled app on premises requests?
Solution: Yes, and AD Agent
Once brought into Okta, LDAP roles are represented as:
Solution: Licences
The SCIM protocol is <response_is_entered_here> for provisioning and managing identity data on the web.
Solution: An application-level SAML protocol
Provisioning actions between cloud-based apps / on-premises apps and Okta are completed by using:
Solution: The OAuth 2.0 standard
PDF + Testing Engine
|
---|
$66 |
Testing Engine
|
---|
$50 |
PDF (Q&A)
|
---|
$42 |
Okta Free Exams |
---|
![]() |