-
Notifications
You must be signed in to change notification settings - Fork 33
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
oauth_providers_example.dart: example needs to be updated #93
Comments
There also seems to be a mismatch between the expected query parameter name ( EDIT: here is a workaround for now if (uri.queryParameters.containsKey('refreshToken')) {
Map<String, String> params = {};
params.addAll(uri.queryParameters);
params['refresh_token'] = uri.queryParameters['refreshToken']!;
client.auth
.completeOAuthProviderSignIn(uri.replace(queryParameters: params));
} else {
client.auth.completeOAuthProviderSignIn(uri);
} |
Hi, We are activity working to improve the SDK. stay tuned. |
Hi, thank you very much for your work! Will this improvements include the migration from the old backend URL discussed in the link below? |
Yes, I am working on it. I think we will make it in the next major release two. |
Unfortunately, using Found a workaround to authenticate with OAuth in Flutter though.
After successful auth, should return with the |
The example now has updated URLs but still doesn't work because it refers to success/failure callback settings, which do not seem to be supported. Is there an updated suggestion for how to implement? |
that part is incorrect, there is no success/failure URLs in hasura-auth, instead, if there is an error, the callback url will include an error query arg describing the issue |
The example's comments give wrong instructions regarding the configuration of NHost's OAuth callbacks:
At line 10 it reads:
wheareas only one callback URL can be set on GitHub settings and no URL can be set on NHost's GitHub provider configuration.
Also at line 23, the sign in URL is wrong. It should look like:
The text was updated successfully, but these errors were encountered: