13 lines
1.2 KiB
Text
13 lines
1.2 KiB
Text
|
|
[[_transient-session]]
|
|
|
|
=== Transient sessions
|
|
|
|
You can conduct transient sessions in {project_name}. When using transient sessions, {project_name} does not create a user session after successful authentication. {project_name} creates a temporary, transient session for the scope of the current request that successfully authenticates the user. {project_name} can run <<_protocol-mappers, protocol mappers>> using transient sessions after authentication.
|
|
|
|
The `sid` and `session_state` of the tokens are usually empty when the token is issued with transient sessions. So during transient sessions, the client application cannot refresh tokens or validate a specific session.
|
|
Sometimes these actions are unnecessary, so you can avoid the additional resource use of persisting user sessions. This session saves performance, memory, and network communication (in cluster and cross-data center environments) resources.
|
|
|
|
At this moment, transient sessions are automatically used just during <<_service_accounts, service account authentication>> with disabled token refresh. Note that token refresh is
|
|
automatically disabled during service account authentication unless explicitly enabled by client switch `Use refresh tokens for client credentials grant`.
|
|
|