<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z00007awZq4CAEOkta Classic EngineSingle Sign-OnAnswered2022-04-27T16:24:30.000Z2022-04-26T07:26:29.000Z2022-04-27T16:24:30.000Z

OhadO.46499 (Customer) asked a question.

Upgrading protocols following the Okta SAML/Provisioning reports

Background: We are doing an in-house review to check which apps can be upgraded for a better Sign on protocol/provisioning. We are currently using the Okta SAML/Provisioning reports (Okta Admin dashboard > Reports > SAML capable apps/Provisioning capable apps.

 

Concern: If I follow the reports suggestion and enable SAML/Provisioning for the listed apps - will there be any effect on currently logged in users? For example a logout, access block or app termination for the users? If so - Is there a sandbox I can use in order to test those upgrades?

I would appreciate any advice in that topic 


  • flaviu.vrinceanu1.5628408972654734E12 (Customer Success Service Delivery)

    Hi @OhadO.46499 (Customer)​,

     

    Thank you for posting on the Okta community page!

     

    The users shouldn't encounter the examples provided by you as Okta does not have control over the application session. Once the user's app session will be closed, the next time the users will log in on the application side, they will be re-directed to Okta for authentication since now the app is configured to use SAML as an SSO method. I have provided bellow a documentation about SAML as well:

     

    Additionally, you can also create a free environment by accessing the link bellow for you to be able to test certain configurations before doing so in your production environment:

     

    I hope the above information is helpful!

    Expand Post
This question is closed.
Loading
Upgrading protocols following the Okta SAML/Provisioning reports