User-Based Authentication Capabilities #9
Merged
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.
This provides support for user-based authentication with
email
andpassword
credentials, where either credentials withpublicKey/privateKey
oremail/password
are supported when creating the API..on('auth', ...)
still functions properly, and clients must callapi.auth()
in order to authenticate. Example:Some of the documentation was also inaccurate and has been fixed to the best of my ability. Most of it was replacing
ForteApi
withcreateApi
.