Sessions
Understand what your application can expect after a user signs in and how to handle expired sessions.
After sign-in
Your application receives the result of a completed authorization flow and establishes the session pattern supported by its integration. Keep session material out of URLs and do not expose server credentials to browser code.
When a session expires
Return the user through the normal Auth flow. If Clikkle Identity still recognizes an eligible central session, the user may continue without entering credentials again.
Protect application routes
Check authenticated state before rendering protected application areas. Send unauthenticated users to your normal sign-in entry point and preserve the page they intended to open.
Was this page useful?