We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The issue is here:
stormpath-sdk-react/src/components/RegistrationForm.js
Line 64 in 6a11c86
The account stores return, but with no authorizeUri. This is what is returned:
{ href: "https://api.stormpath.com/v1/directories/...", name: "My Application Google Directory", provider: { clientId: "...-......apps.googleusercontent.com", href: "https://api.stormpath.com/v1/directories/...../provider", providerId: "google", scope: "email profile" } }
Please note that this DOES work using the express-stormpath-sample-project example.
express-stormpath-sample-project
Is this library broken?
The text was updated successfully, but these errors were encountered:
Trying to follow the client API myself e.g. going to https://easy-shell.apps.stormpath.io/authorize?response_type=stormpath_token&account_store_href=https://api.stormpath.com/v1/directories/... does indeed go to a Google OAuth page, and then redirects back with a JWT response. But this doesn't help this example or the React project, rather it is the Client API.
Sorry, something went wrong.
I'm experiencing the same issue. I have lost login functionality.
Indeed this lib iterates over social providers and accepts only those with authorizeUri. How to configure this option?
temporary workaround - revert to 1.3.4
No branches or pull requests
The issue is here:
stormpath-sdk-react/src/components/RegistrationForm.js
Line 64 in 6a11c86
The account stores return, but with no authorizeUri.
This is what is returned:
Please note that this DOES work using the
express-stormpath-sample-project
example.Is this library broken?
The text was updated successfully, but these errors were encountered: