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

• A.No
• B.Yes

Comment: *

Name: *

Email: *

Verification: *

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

• A.No
• B.Yes

Comment: *

Name: *

Email: *

Verification: *

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

• A.Yes
• B.No

Comment: *

Name: *

Email: *

Verification: *

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: Both statements are true

• A.No
• B.Yes

Comment: *

Name: *

Email: *

Verification: *

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

• A.Yes
• B.No

Comment: *

Name: *

Email: *

Verification: *