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
With #3125 we have decided to implement Auth0 as the new authentication tool for Flow and Lumen. This change will give us the possibility to have single sign-on available on the products and move away from the Google account user requirement there is today.
Why do we add this issue
With moving the Auth0 we have the opportunity to create a new login page for Flow and Lumen (one) that follows the new Akvo brand and give a stepping stone to how the products will adjust to the brand.
The aim is to show that Flow and Lume are Akvo products and part of the overall Data journey approach we are promoting in the international development sector.
Problem or idea
What is the current status quo
On https://akvoflow-dev1.appspot.com/ by clicking on the larger 'Log in' button you will be brought to the AuthO log in page. There you can choose to log in with your Google account or with your email and a password. This page needs to follow the Akvo brand.
User journey
We will not change how users become users on the product. For anyone to have access to Flow and Lumen, the workspace admin has to add this user to the instance/tenant with the user's Name and Email address and set his/her role and permissions. Then the user can access the instance/tenant and log in.
For existing users there will be two options:
Login with Google --> In this case, nothing changes. User lands on the login page and clicks to log in with Google
Login with another email --> In this case, the new user account needs to be set up:
user admin changes the google email to the new email address
user goes to Flow
user cannot Log in as she does not have a password, so she clicks to # and uses her email and creates a password. If anyone signs up to a Flow instance but is not added as a user to Flow, she will be able to create an Auth0 user account but will not have access and will land on another page: Rebrand user access denied page #3141
If the change is successful what might we observe?
We believe that moving to Auth0 will have two positive consequences:
more Flow users will access Lumen
move Flow users will move away from their Google accounts to their organisational accounts (as it has been a known pain for Flow users to have to create Google accounts to use the product)
Solution or next step
Create a new UI following the new Akvo brand for the login page
The text was updated successfully, but these errors were encountered:
updated on 19 July after a talk with Dan on the status of things, see notes here: https://docs.google.com/document/d/1uE4tc_Bz-nooJdDqP8L3Qe_ZuoOOAD9-WoNsvjKq7v0/edit#
Context
With #3125 we have decided to implement Auth0 as the new authentication tool for Flow and Lumen. This change will give us the possibility to have single sign-on available on the products and move away from the Google account user requirement there is today.
Why do we add this issue
With moving the Auth0 we have the opportunity to create a new login page for Flow and Lumen (one) that follows the new Akvo brand and give a stepping stone to how the products will adjust to the brand.
The aim is to show that Flow and Lume are Akvo products and part of the overall Data journey approach we are promoting in the international development sector.
Problem or idea
What is the current status quo
On https://akvoflow-dev1.appspot.com/ by clicking on the larger 'Log in' button you will be brought to the AuthO log in page. There you can choose to log in with your Google account or with your email and a password. This page needs to follow the Akvo brand.
User journey
We will not change how users become users on the product. For anyone to have access to Flow and Lumen, the workspace admin has to add this user to the instance/tenant with the user's Name and Email address and set his/her role and permissions. Then the user can access the instance/tenant and log in.
For existing users there will be two options:
If the change is successful what might we observe?
We believe that moving to Auth0 will have two positive consequences:
Solution or next step
Create a new UI following the new Akvo brand for the login page
The text was updated successfully, but these errors were encountered: