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
We now have Auth0 running on test, meaning we can take the next steps towards removing Keycloak for user authentication in Lumen.
Why do we add this issue?
We want to make sure that the Auth0 change is:
as smooth as possible in terms of as least possible obstruction to existing users as we can make with sufficient communication
unifies Flow and Lumen a bit more in terms of user accounts, look and feel and workflows
we do not remove the important features out of the blue
we keep the changes as simple and minimal as possible to be able to improve the UX in later iterations
Problem or idea
If any user tries to # or log in to a Lumen tenant she has not been added to by the organisational admin we need a page to inform her that, she does not have access to this Lumen tenant and should ask her organisational admin to add her.
Status quo
If you log in using an existing Keyloak user to a Lumen tenant this user does not have access to you see the screen below.
Solution or next step
With this issue, we want to make sure users see the same thing when trying to access Flow as when they try to access Lumen. As the text needs to reflect the product you are accessing we have two separate issues, one for Flow and one for Lumen. But the pages should be as identical as possible. Furthermore, the user should see the same thing if she is logging in with and Auth0 account or with a Google account.
Context
We now have Auth0 running on test, meaning we can take the next steps towards removing Keycloak for user authentication in Lumen.
Why do we add this issue?
We want to make sure that the Auth0 change is:
Problem or idea
If any user tries to # or log in to a Lumen tenant she has not been added to by the organisational admin we need a page to inform her that, she does not have access to this Lumen tenant and should ask her organisational admin to add her.
Status quo
If you log in using an existing Keyloak user to a Lumen tenant this user does not have access to you see the screen below.

Solution or next step
With this issue, we want to make sure users see the same thing when trying to access Flow as when they try to access Lumen. As the text needs to reflect the product you are accessing we have two separate issues, one for Flow and one for Lumen. But the pages should be as identical as possible. Furthermore, the user should see the same thing if she is logging in with and Auth0 account or with a Google account.
Related issue for Flow: akvo/akvo-flow#3141
The text was updated successfully, but these errors were encountered: