Branded uniform method of user timeout/logout with redirection to a stable login location (SSO)

Mark Ryan

Having searched through some of the ideas here on the lab I have seen this topic spoken about a few different ways. In OAS 2024 we are seeing where a user's session is timed out they are sent to a default Oracle Sign in page.

../bi-security-login/login.jsp

Not only is it not branded, the issue is that our users are authenticated through SSO and do not have Oracle managed credentials so this screen is not helpful to them.

I did read some other references here but it came with Notes

https://docs.oracle.com/en/cloud/paas/analytics-cloud/acabi/configure-advanced-system-settings.html#GUID-C937ABAA-5474-4659-9069-13389EF41DA5

We've attempted some modification in our development environments and while some behavior can be altered, we've found that this introduces other issues when we are trying to access OAS directly through other applications using named user with system credentials (not SSO). We've also seen warnings where this is 'not supported' by Oracle. One would think that you could simply update the session logout/login page with a redirect to a desired location an have it come in with a fresh session. (regardless of what node it comes from (as we are multi node).

We have had discussions and SR with Oracle but this seems like something that should be easily configurable and part of the admin console. So are we just missing something here? If not, It would be great to simplify the location of an alternate landing location