Details
-
Bug
-
Resolution: Fixed
-
Major
-
2.15.0
-
None
-
Unit
-
Unknown
-
N/A
-
Description
The OAuth2 authorization of a client configuration (used by extensions to get tokens to call an external service on behalf of the user) uses the same session storage as the OpenID Connect authentication, and starting it (as well as receiving its callback) clears it.
So when a user authenticated through OpenID Connect authorizes an OAuth2 client configuration, the information of the authentication is lost from the session: the access, refresh and ID tokens, and which configuration was used to authenticate. As a consequence, for the rest of the session:
- the logout is sent to the provider of the OAuth2 client configuration (or not at all), without ID token
- the user information is not refreshed anymore
- the configuration properties are read from the OAuth2 client configuration instead of the authentication one
The OAuth2 authorization should not touch the authentication session information.
Attachments
Issue Links
- relates to
-
OIDC-204 Add support for OAuth2 Authorization Code Flow
-
- Closed
-