Hi,
We have several applications in the same portal. It started on traditional but now we have several in reactive.
The single sign on works fine, but we have problems in the login expiration time.
Use case:
Login and started to work on a traditional application.
If I don't use any reactive page for more than login session timeout defined, when I click on a reactive page I get no login session exception (in my case, a redirection to login page).
It's a normal behavior?
How can I extend the reactive login session when using the traditional?
Thank you
Hi Luis,
Just to better understand your issue, you have no problem with cross-application usage correct? Meaning that after login, you can navigate and use both types of applications (reactive vs traditional) without any issue.
Your issue is that the session expires on the traditional, redirecting the user to the login page, but the same doesn't occur on the reactive applications?
Regards,
PZ
Hi Paulo,
Both redirect well to login.
But if I stay long time on traditional part when I click on a reactive page, I'll get a timeout and a redirection to login.
Luis
Alright, please check the workaround we did, perhaps it can work for you too.
Regards
I've noticed that in the past, where one session expired but the other not... however I never tried to address it or find a workaround... Have you tried to do a silent login before the navigation across different app types? If that works you can improve it, like saving the login DateTime in local storage using JS, this way you can to keep track of the session in both stacks and only do the login when needed.
Cheers,
Rúben
We did a workaround related to the issue you are referring @Ruben Meireles. I was just trying to confirm if the issue was exactly what I was thinking.
So, on the login, we stored a token(GUID) and its expiration time. And then we put that token on a cookie. Although it is exposed on the browser, there's no other info other than a bunch of characters.
Then, on the OnApplicationReady system event, we check if the session is active and if that token on the cookie matches the one we previously stored.
If not, the user is logged out and redirected to the login screen.
That was our workaround, but I'm sure there are others.
Nice! That's a cool approach @Paulo Zacarias 👍
Everytime this action occurs you update the expirationDate, Right?
I'll try it and give you news.
Thank you.