This repository has been archived by the owner on Feb 22, 2024. It is now read-only.
Support passwordless JSON logins #515
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Only the first phase of the passwordless login supported JSON based requests. The login itself, usually done by clicking on the link in the login email, supported only html requests and always responded with a `Set-Cookie` header. Now the login itself can be sent with `application/json` in the `Accept` header resulting in a JSON response that contains `authorization_token` in the `user` attribute contained in the `response` attribute.
This allows API servers to override of the server address in the template.
when we are passwordless and we get an email of a non-regitered email we create the user.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Only the first phase of the passwordless login supported JSON based requests.
The login itself, usually done by clicking on the link in the login email,
supported only html requests and always responded with a
Set-Cookieheader.Now the login itself can be sent with
application/jsonin theAcceptheaderresulting in a JSON response that contains
authorization_tokenin theuserattribute contained in theresponseattribute.