-
Notifications
You must be signed in to change notification settings - Fork 6
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
Feature/invite with digid #231
Conversation
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.
@vaszig Thanks for catching it! Two contacts (yours and reverse) were created and they were not deduplicated correctly |
Works fine, thanks! Glad you're able to round this up properly. Feedback from my testing:
Point 2 can be completed within this PR, 1+3 can be done in separate ones. |
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'd like a bit more attention to the user interface when confirming the invitation. The DigiD-only option shouldn't be screen-wide, and the DigiD+username option should make clear that you can register via one or the other. My suggestion would be to put both options next to each other (left vs right).
@alextreme I placed registration with Digid and with email into two columns next to each other |
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.
The styling seems a bit weird to me because of the big difference concerning the height. I would align the two cards vertically (like we do on the login page), but of course this is my opinion!
Putting it next to eachother was as requested from my end, lets see during UAT if anyone minds as it is a bit inconsistent. |
task - https://taiga.maykinmedia.nl/project/open-inwoner/task/472
Creating inactive user along with the contact finally shot us in the foot :)
The old process:
The problem with this process:
If we allow registering with Digid, when we will have two users: the one signed up with Digid and inactive one, because the Digid user email is created automatically based on their BSN
Possible solution:
Don't create inactive user when the contact is created and update the contact after the user is registered (with or without Digid)
The new process: