-
Notifications
You must be signed in to change notification settings - Fork 117
Meteor auth migration guide #334
Comments
This looks awesome, let me know if you ever get around to it. |
I just leave this here: I am currently going through Meteors accounts-base, accounts-oauth, .. and I am getting kind a lost. There are many fragments bound to Meteor and are already available (in there own way) to Feathers. I am currently thinking about a simple hook type of system that obtains a Strategy and a token. Have you done any research on the requirements you could share? |
I've looked into feathers authentication and it's really straightforward. There aren't any real "requirements", just read the docs and acclimate yourself. The main reason Meteor developers get frustrated with it is because Meteor does practically everything for the developer, handicapping him/her to the system. It sounds like you're dealing with an existing application - in which case you could either do a database schema migration or configure the existing feathers packages to work with your current user schema. |
I ended up using |
I think I'm going to close this out. @marshallswain if you have the time and it becomes something you want to tackle, feel free to re-open. :) |
This is just something that I'm interested in doing, so if I've gotten busy and haven't done anything here in two months, please ping me and we might close it. :)
The tutorial: https://themeteorchef.com/recipes/roll-your-own-authentication/
The GitHub repo: https://github.com/themeteorchef/roll-your-own-authentication/tree/master/code
And here's a basic MongoDB doc that Meteor would create should you choose to use their
accounts-password
package.The text was updated successfully, but these errors were encountered: