Skip to content
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

Integrating with arbitrary user authentication systems #30

Open
jwarkentin opened this issue Nov 9, 2014 · 0 comments
Open

Integrating with arbitrary user authentication systems #30

jwarkentin opened this issue Nov 9, 2014 · 0 comments
Assignees

Comments

@jwarkentin
Copy link
Owner

It would be interesting and useful to be able to integrate with any user authentication system for any application that wants to use node-monkey. This may be possible by allowing users to be authorized through one or two different methods.

Method 1
Allow application to pass in user auth and permission data through the config when initializing. This is somewhat limited because it would require pre-loading all users into the config, even if there are a lot. Additionally, I don't know how password verification would work unless node-monkey just supported a lot of different password authentication schemes. This is likely not the approach to take.

Method 2
Allow the application to pass in an authorize callback which will be passed any credentials when a user desires to have access. It will also be given a callback which must be called with true|false indicating authorization and the list of commands the user has authorization to run, if true. This is likely the best approach and will be used unless something better comes to mind.

Note that any of the above authentication methods would likely only supplement any user accounts added via the official authentication mechanism built in to node-monkey.

Also, this system should play nicely with oauth. I'm not sure it would ever be a problem but it should be considered when developing it.

@jwarkentin jwarkentin added this to the v0.3.0 milestone Nov 9, 2014
@jwarkentin jwarkentin self-assigned this Nov 9, 2014
@jwarkentin jwarkentin removed this from the v0.3.0 milestone Jul 22, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant