I wouldn't recommend on having a background keep alive using the update
token. Rather, just rely on the user performing actions to keep the session
alive and configure the SSO idle timeout accordingly to your needs.
With regards to remember me I don't understand your question as there is no
difference here. Remember me only sets a persisted cookie so session
survives a browser restart as well as recently we've introduce options to
have different SSO idle and max for remember me sessions.
On Fri, 4 Jan 2019 at 07:24, Alex Chatziparaskewas <
alex.chatziparaskewas(a)trapezegroup.com> wrote:
Hi All,
We are using the keycloak javascript adapter. In the same way as the token
and refresh token can be updated gracefully in the background using its
updateToken method, is there any means by which the same can be done to a
'remember me' session?
Thanks & Regards,
Alex
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user