Skip to content

Improve user flow when logging in #173

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wotwot563 opened this issue Jun 3, 2020 · 0 comments · Fixed by #174
Closed

Improve user flow when logging in #173

wotwot563 opened this issue Jun 3, 2020 · 0 comments · Fixed by #174
Assignees

Comments

@wotwot563
Copy link

Is your feature request related to a problem? Please describe.
When the user clicks on the login button, they click on the 'FHICT' button, then get redirected to the backend Identity server, where they have to click "Fontys" again. This is quite confusing for the end-user.

Describe the solution you'd like
Upon clicking "Login with FHICT" in the frontend, automatically redirect them through the identity server to the Fontys identity server.
This way the user does not see the unstyled IdentityServer, this will improve usability.

It would be preferred if we could make a general way of handling this so we can easily add "Login with Surfcontext" in the future, without having the user going to our Identity server again. Making a re-usable implementation of this streamlines the future login implementations.

Additional context
Some people will still need to login with the "local login" in the identity server, we will probably need a new button for this on the frontend "Login with Identity Server" and a flow that does not redirect them through our Identity Server but that uses the old flow.

This issue will require changes in both the backend and in the frontend.

@wotwot563 wotwot563 self-assigned this Jun 3, 2020
@wotwot563 wotwot563 mentioned this issue Jun 3, 2020
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant