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
When a user logs into lowcoder through oauth provider into one org, logs out, and logs into a different org, this causes an error.
It seems the connection data stored in the db is not handled in a way that facilitates a user to log into different orgs.
Our setup: Keycloak with multiple orgs. Users can exist on both orgs.
Lowcoder Generic Oauth Provider.
Expected Behavior
If a user logs out, and logs back in through a different org, the system should be able to handle this case without causing an error.
Steps to reproduce
Have a multitenant setup in your IDP.
Register the same user in 2 orgs. Same name, email, etc.
Set up the Generic Oauth provider to authenticate through keycloak.
Log into lowcoder using org 1.
Log out of org 1.
Log into org 2.
This should cause an error.
Environment
Lowcoder version 2.4.x
Keycloak IDP
Additional Information
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Current Behavior
When a user logs into lowcoder through oauth provider into one org, logs out, and logs into a different org, this causes an error.
It seems the connection data stored in the db is not handled in a way that facilitates a user to log into different orgs.
Our setup: Keycloak with multiple orgs. Users can exist on both orgs.
Lowcoder Generic Oauth Provider.
Expected Behavior
If a user logs out, and logs back in through a different org, the system should be able to handle this case without causing an error.
Steps to reproduce
Have a multitenant setup in your IDP.
Register the same user in 2 orgs. Same name, email, etc.
Set up the Generic Oauth provider to authenticate through keycloak.
Log into lowcoder using org 1.
Log out of org 1.
Log into org 2.
This should cause an error.
Environment
Lowcoder version 2.4.x
Keycloak IDP
Additional Information
No response
The text was updated successfully, but these errors were encountered: