This repository has been archived by the owner on May 31, 2024. It is now read-only.
Account/auth features available outside DDP using GraphQL #2530
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.
Note: this authentication mode through graphql is NOT compatible with DDP. If you actually use Meteor methods and publication system, instead use the traditionnal auth workflow with Accounts. Vulcan's login form will probably keep using Meteor methods.
This features targets other types of non-meteor clients like React Native, Next and so on.
This is an experimental feature, not yet secured. Use at your own risk and take time to read the code. Inputs welcome :)
To test: test should be doable using directly GraphQL Playground. To pass a token: provide HTTP header
Relevant discussion:
#1896
See example usage (not yet done but still a good demo of how to consume this API):
https://github.com/VulcanJS/vulcan-next-starter
Reusing Meteor server methods:
meteor/meteor#10937