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 authorizes the users, while the IDP authenticates them
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
What does SCIM stand for?
Solution: System for Cross-domain Identity Management
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
When does Okta bring LDAP groups into Okta?
Solution: Only during an LDAP import
With Okta you federate the 'Office 365 tenant name' (which is the default Microsoft domain you have) or the 'Office 365 domain'?
Solution: You federate with Okta only the 'Office 365 domain'
How can SAML provision attributes via JIT? Or even create users?
Solution: By including specific information in the assertion
When using Okta Expression Language, which variable type results out of this Okta Expression? isMemberOfGroup("groupId")
Solution: Boolean
Does Okta require an Agent to sit in-between Okta to SCIM-enabled app on premises requests?
Solution: Yes, an Okta Provisioning Agent
The SCIM protocol is
Solution: An application-level SAML protocol
