This issue has been created
There is 1 update.
 
 
OpenId Connect / cid:jira-generated-image-avatar-fd1e9e83-83d0-45ca-9962-2b66c4a85894 OIDC-344 Open

Authorizing an OAuth2 client configuration loses the OpenID Connect authentication information of the session

 
View issue   ยท   Add comment
 

Issue created

 
cid:jira-generated-image-avatar-f5837bb9-3bfe-48cc-b744-55a2eef70a17 Thomas Mortagne created this issue on 19/Nov/26 10:59
 
Summary: Authorizing an OAuth2 client configuration loses the OpenID Connect authentication information of the session
Issue Type: cid:jira-generated-image-avatar-fd1e9e83-83d0-45ca-9962-2b66c4a85894 Bug
Affects Versions: 2.15.0
Assignee: Unassigned
Components: Authenticator
Created: 19/Nov/26 10:59
Priority: cid:jira-generated-image-static-major-c1da4645-7baa-4115-80f7-36ad4d864589 Major
Reporter: Thomas Mortagne
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.

 
 

1 update

 
cid:jira-generated-image-avatar-f5837bb9-3bfe-48cc-b744-55a2eef70a17 Changes by Thomas Mortagne on 19/Nov/26 10:59
 
Assignee: Thomas Mortagne