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
Replace verification form with FEIDE auth #4063
Conversation
endpoint: `/oidc/validate/?code=${code}&state=${state}`, | ||
method: 'GET', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm considering changing this to a POST. There isn't really much practical difference here, more of a design choice.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, it doesn't matter much but I think a POST would make more sense.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think keeping it as a GET
is fine
c08ec09
to
f3a0ad3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work! 🏅
8cf213f
to
5eeb4da
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just noticed it would be nice if you would use the Card.Header
as card headers instead of a custom one.
Navigation around user settings was a bit difficult and hard to find. This should make it easier to navigate to the settings page and back.
The user now just authenticates with FEIDE and we handle the rest automatically.
LGTM |
Description
Feide verification 😬
Result
Start page
No valid study programmes:
Screencast.from.2023-07-30.18-12-10.webm
Valid study programme:
Notice that the result from the previous verification is still present. The user may re-verify with correct data to get the proper result.
Screencast.from.2023-07-30.18-14-34.webm
Testing
Please describe what and how the changes have been tested, and provide instructions to reproduce if necessary.
Resolves ABA-521