You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
User B is signed in as User A, causing incorrect user authentication.
Expected Behavior
User B should be signed in as themselves after authenticating via the OAuth provider, not as User A.
Steps to reproduce
Set up a generic OAuth provider.
Sign in using the OAuth provider with User A.
Open an incognito window and attempt to sign in with User B using the same OAuth provider.
Observe that User B is signed in as User A instead of their own account.
Environment
Lowcoder version 2.4.10 is affected, but it's likely that the issue also impacts the latest version.
mode: ENTERPRISE
Additional Information
We use Keycloak as the OAuth provider to authenticate across multiple Keycloak realms. However, since Lowcoder doesn’t support multiple Keycloak providers, we had to configure separate generic OAuth providers, each representing a different Keycloak realm.
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Current Behavior
User B is signed in as User A, causing incorrect user authentication.
Expected Behavior
User B should be signed in as themselves after authenticating via the OAuth provider, not as User A.
Steps to reproduce
Environment
Lowcoder version 2.4.10 is affected, but it's likely that the issue also impacts the latest version.
mode: ENTERPRISE
Additional Information
We use Keycloak as the OAuth provider to authenticate across multiple Keycloak realms. However, since Lowcoder doesn’t support multiple Keycloak providers, we had to configure separate generic OAuth providers, each representing a different Keycloak realm.
The text was updated successfully, but these errors were encountered: