-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Add support for custom scopes to federated logins #297
Comments
@ceich yeah sure that's a really good enhancement to the library. |
Any update on this? Definitely something I would like added |
if no ones working on this id like to pick it up |
If anyone has something I can NPM install that allows for this, I would be eternally grateful. I tried forking the library, building it with the directions in the wiki then installing it with npm to no avail. Ended up ripping out the built-in Facebook login and replacing it with https://serverless-stack.com/chapters/facebook-login-with-cognito-using-aws-amplify.html which works great. |
@peetss @stephenhuh @dcsena @ceich we are looking at an enhancement for I'd be interested in seeing what you expect the overloaded scope experience would look like in a more simplified API. Could you please comment in the RFC? |
I ended up not using custom scopes as they are quite a pain to get approval for on Facebook in particular. However, it would still be nice to pass additional scopes in optionally. Will check out the RFC. |
Is this functionality still needed with the latest updates to the CLI supporting the OAuth/Hosted UI (where you can specify scopes in the OAuth config) as well as the library supporting OAuth with |
Agree it's ok to close. |
This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs. Looking for a help forum? We recommend joining the Amplify Community Discord server |
What is the current behavior?
What is the
expecteddesired behavior?I have forked the repo and am willing to add support. Let me know if this would be welcome.
The text was updated successfully, but these errors were encountered: