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
The email change of a user logged in with Keycloak is currently not correctly handled by REANA.
Let's consider an user with email [email protected]. When logging in for the first time, a new user is created both in Invenio's and in REANA's tables, with the correct email:
If this user changes his email, for example to [email protected], then a new user is created in REANA's table, while Invenio keeps using the old user. Given that authentication in reana-ui is handled by Invenio, the user is still able to see his workflows and to use his access token.
However, REANA should not create a new user with the new email provided by Keycloak. We should also check whether it is necessary to update the email in REANA's user table.
The text was updated successfully, but these errors were encountered:
The email change of a user logged in with Keycloak is currently not correctly handled by REANA.
Let's consider an user with email
[email protected]
. When logging in for the first time, a new user is created both in Invenio's and in REANA's tables, with the correct email:If this user changes his email, for example to
[email protected]
, then a new user is created in REANA's table, while Invenio keeps using the old user. Given that authentication in reana-ui is handled by Invenio, the user is still able to see his workflows and to use his access token.However, REANA should not create a new user with the new email provided by Keycloak. We should also check whether it is necessary to update the email in REANA's user table.
The text was updated successfully, but these errors were encountered: