Mar 21 2018 09:37 AM
After rolling out Office 365 and federating with Okta its seems to be very unstable as far as holding peoples sessions (mainly to OWA) Wondering if anyone has any advice. I do not remember having these issues with the old sign in experience from Microsoft.
Here are a few details:
OWA is not holding sessions for very long and sometimes folks get session timeout messages. On google the sessions held for several days even if the machine or browser was closed.
Outlook 2016 is constantly prompting people to log back in to Okta which is a more recent issue.
In general, it seems like people are constantly having to login to SSO for various office 365 apps. I do not believe its an Okta issue as thats only getting presented after users are kicked out of Office 365.
Mar 21 2018 11:21 AM
That looks like the type of issue you have to address with Okta support.
The default O365 session timeouts are listed here: https://support.office.com/en-us/article/session-timeouts-for-office-365-37a5c116-5b07-4f70-8333-5b8...
Some of these can be modified on the customer side (i.e. the OWA timeout), but they are all dependent on the identity provider (Okta in your case).
Mar 21 2018 12:30 PM
Mar 22 2018 01:03 AM
If you mean that the issue started occurring after they introduced the new sign-in page, I agree, that's most likely something on O365's side. @Kelvin Xia might be able to help with that. Or better yet, open a support case.
Mar 22 2018 11:47 AM
It would be best to open a support case for this as it isn't clear that it's directly related to the new sign-in experience.