-
Notifications
You must be signed in to change notification settings - Fork 27
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
A user can sign up #6
Comments
marein
added a commit
that referenced
this issue
Mar 11, 2018
marein
added a commit
that referenced
this issue
Mar 11, 2018
marein
added a commit
that referenced
this issue
Mar 11, 2018
marein
added a commit
that referenced
this issue
Mar 20, 2018
The work in the identity context is done. Next step is to build the user interface for this task. |
marein
added a commit
that referenced
this issue
Aug 7, 2019
Without the ApplicationLifeCycle the UserService itself becomes cleaner. This is due to less indentations. Furthermore, the mediator also has a validation decorator which could be leveraged to validate incoming messages.
marein
added
priority:medium
domain:identity
priority:low
and removed
priority:medium
labels
Apr 19, 2022
marein
added a commit
that referenced
this issue
Oct 16, 2022
Upon arrival, ArrivialAuthenticator creates a new user in the identity context and authenticates them in the session. The current implementation covers what AssignUserIdOnKernelRequest did before. It adds some complexity, but opens the way for #130 to secure the /metrics endpoint with basic auth, and #6 to eventually authenticate the user in any way.
marein
added a commit
that referenced
this issue
Oct 16, 2022
Upon arrival, ArrivialAuthenticator creates a new user in the identity context and authenticates them in the session. The current implementation covers what AssignUserIdOnKernelRequest did before. It adds some complexity, but opens the way for #130 to secure the /metrics endpoint with basic auth, and #6 to eventually authenticate the user in any way.
marein
added a commit
that referenced
this issue
Oct 16, 2022
Upon arrival, ArrivialAuthenticator creates a new user in the identity context and authenticates them in the session. The current implementation covers what AssignUserIdOnKernelRequest did before. It adds some complexity, but opens the way for #130 to secure the /metrics endpoint with basic auth, and #6 to eventually authenticate the user in any way.
marein
added a commit
that referenced
this issue
Oct 26, 2022
Upon arrival, ArrivialAuthenticator creates a new user in the identity context and authenticates them in the session #153. The current implementation covers what AssignUserIdOnKernelRequest did before. It adds some complexity, but opens the way for #130 to secure the /metrics endpoint for php with basic auth, and #6 to eventually authenticate the user in any way.
marein
added a commit
that referenced
this issue
Jul 19, 2024
Remove passwords from the signup process and define email and username as required fields. Also make use of the validation middleware to receive only usable data within the handler. As it will be a 3-step signup process with an email verification in-between, it's possible to run the signup without persisting data to trigger only the validation #6.
marein
added a commit
that referenced
this issue
Jul 19, 2024
Remove passwords from the signup process and define email and username as required fields. Also make use of the validation middleware to receive only usable data within the handler #6.
marein
added a commit
that referenced
this issue
Jul 19, 2024
Add a centered layout for the signup and login pages #6. Additionally, add progressive enhancement for forms and improve the handling of anchors, depending on whether a sticky header is in the markup.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After playing for a while, the user decides to create an account and wants to sign up. They must provide an email (for passwordless auth) and choose a username. Their anonymous account will be used so they take their already played games with them. Email and username must be unique in the system. Username should be 3-20 characters and shouldn't contain spaces.
The text was updated successfully, but these errors were encountered: