What to use on GoogleSignInOptions, requestIdToken or requestServerAuthCode, to achieve Authorization code...
up vote
0
down vote
favorite
I have implementing the Android Google authentication using google.android.gms.auth.
In the setting for GoogleSignInOptions I used till now requestIdToken, with the understanding that this implements OAuth2 Authorization Code flow. This means that it should be using what is known in OAuth2 RFC as response_type=code, code-based that later is validated in the backed.
But digging more into this, I just saw that there is another option requestServerAuthCode, and by looking at it is closer to what I thought I am doing.
Which of these achieves OAuth2 Authorization Code Flow?
Thanks!
add a comment |
up vote
0
down vote
favorite
I have implementing the Android Google authentication using google.android.gms.auth.
In the setting for GoogleSignInOptions I used till now requestIdToken, with the understanding that this implements OAuth2 Authorization Code flow. This means that it should be using what is known in OAuth2 RFC as response_type=code, code-based that later is validated in the backed.
But digging more into this, I just saw that there is another option requestServerAuthCode, and by looking at it is closer to what I thought I am doing.
Which of these achieves OAuth2 Authorization Code Flow?
Thanks!
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have implementing the Android Google authentication using google.android.gms.auth.
In the setting for GoogleSignInOptions I used till now requestIdToken, with the understanding that this implements OAuth2 Authorization Code flow. This means that it should be using what is known in OAuth2 RFC as response_type=code, code-based that later is validated in the backed.
But digging more into this, I just saw that there is another option requestServerAuthCode, and by looking at it is closer to what I thought I am doing.
Which of these achieves OAuth2 Authorization Code Flow?
Thanks!
I have implementing the Android Google authentication using google.android.gms.auth.
In the setting for GoogleSignInOptions I used till now requestIdToken, with the understanding that this implements OAuth2 Authorization Code flow. This means that it should be using what is known in OAuth2 RFC as response_type=code, code-based that later is validated in the backed.
But digging more into this, I just saw that there is another option requestServerAuthCode, and by looking at it is closer to what I thought I am doing.
Which of these achieves OAuth2 Authorization Code Flow?
Thanks!
edited Nov 5 at 3:40
asked Nov 5 at 2:00
user3053247
232413
232413
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
With the ID token flow, you're only using Google Sign In to obtain the identity of the user. See https://android-developers.googleblog.com/2016/01/using-google-sign-in-with-your-server.html.
To use authorization codes, typically with your server, see https://android-developers.googleblog.com/2016/02/using-credentials-between-your-server.html
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
With the ID token flow, you're only using Google Sign In to obtain the identity of the user. See https://android-developers.googleblog.com/2016/01/using-google-sign-in-with-your-server.html.
To use authorization codes, typically with your server, see https://android-developers.googleblog.com/2016/02/using-credentials-between-your-server.html
add a comment |
up vote
0
down vote
With the ID token flow, you're only using Google Sign In to obtain the identity of the user. See https://android-developers.googleblog.com/2016/01/using-google-sign-in-with-your-server.html.
To use authorization codes, typically with your server, see https://android-developers.googleblog.com/2016/02/using-credentials-between-your-server.html
add a comment |
up vote
0
down vote
up vote
0
down vote
With the ID token flow, you're only using Google Sign In to obtain the identity of the user. See https://android-developers.googleblog.com/2016/01/using-google-sign-in-with-your-server.html.
To use authorization codes, typically with your server, see https://android-developers.googleblog.com/2016/02/using-credentials-between-your-server.html
With the ID token flow, you're only using Google Sign In to obtain the identity of the user. See https://android-developers.googleblog.com/2016/01/using-google-sign-in-with-your-server.html.
To use authorization codes, typically with your server, see https://android-developers.googleblog.com/2016/02/using-credentials-between-your-server.html
answered Nov 6 at 4:01
user2705223
1773
1773
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53147373%2fwhat-to-use-on-googlesigninoptions-requestidtoken-or-requestserverauthcode-to%23new-answer', 'question_page');
}
);
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password