<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
0D54z000087zJiFCAUOkta Classic EngineIntegrationsAnswered2024-04-16T10:48:47.000Z2022-09-20T23:56:54.000Z2022-09-21T23:47:53.000Z

poq7r (poq7r) asked a question.

End-Users forced to reauthenticate into Outlook ONLY after WS-Fed

I understand after WS-Fed between Okta and O365 is implemented, users will be asked to reauthenticate via Okta if the session expires, which is set on O365's end. However, after I implemented this, it forced all my users to reauthenticate into Outlook only -- all other apps, it's fine.

 

Anyone know why this occurred?


  • Hello @poq7r (poq7r)​ Thank you for reacting out to our Community!

     

    The authentication prompt has a delay after federation, the prompt for authentication would be delayed by up to 15-30 minutes. If this did not happed, the session token could have refreshed for all apps when the users were prompted for Office re-authentication.

    The session lifetime is not controlled by Okta, even after federation and this might be expected behaviour for the other apps, as some applications to not ask for re-authentication after they have been federated with Okta and the session is continued until killed from the Service Provider side.

    You might want to check this behaviour with MS support, as they would be the ones to provide the required information.

     

    The Okta Community Catalysts Program is now live. Collect online badges when you participate in the Okta Help Center Questions community. Learn more here.

    Expand Post
This question is closed.
Loading
End-Users forced to reauthenticate into Outlook ONLY after WS-Fed