Nikunjpatel890 / socialauth

Automatically exported from code.google.com/p/socialauth
0 stars 0 forks source link

Missing ext2.request_token in google responses when using google provider #304

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1.
Create an app with socialauth
2.
Configure google parameters
3.
Try to login

What is the expected output?
I expect in the callback contains:
&openid.ns.ext2=xxxxx
&openid.ext2.scope=xxxxx
&openid.ext2.request_token=xxxxx

What do you see instead?
Only the ext1 variables are contained, not the ext2. Therefore I get an 
exception when executing connect in the SocialAuthManager:

org.brickred.socialauth.exception.SocialAuthException: Key in Request Token is 
null or blank
    at org.brickred.socialauth.util.OAuthConsumer.getAccessToken(OAuthConsumer.java:231) ~[socialauth-4.2.jar:na]
    at org.brickred.socialauth.oauthstrategy.Hybrid.verifyResponse(Hybrid.java:138) ~[socialauth-4.2.jar:na]
    at org.brickred.socialauth.oauthstrategy.Hybrid.verifyResponse(Hybrid.java:115) ~[socialauth-4.2.jar:na]
    at org.brickred.socialauth.provider.GoogleImpl.doVerifyResponse(GoogleImpl.java:172) ~[socialauth-4.2.jar:na]
    at org.brickred.socialauth.provider.GoogleImpl.verifyResponse(GoogleImpl.java:161) ~[socialauth-4.2.jar:na]
    at org.brickred.socialauth.SocialAuthManager.connect(SocialAuthManager.java:184) ~[socialauth-4.2.jar:na]

What version of the product are you using? On what operating system?

socialauth 4.2, java 1.7

Original issue reported on code.google.com by floz...@gmail.com on 11 Oct 2013 at 2:50

GoogleCodeExporter commented 8 years ago
Please have a look into following issue

http://code.google.com/p/socialauth/issues/detail?id=298

Original comment by tarun.na...@3pillarglobal.com on 11 Oct 2013 at 3:19

GoogleCodeExporter commented 8 years ago
That was fast... thank you. We will try. Maybe it's sth worth mentioning in the 
documentation...

Original comment by floz...@gmail.com on 11 Oct 2013 at 3:24

GoogleCodeExporter commented 8 years ago
It was fixed

Original comment by floz...@gmail.com on 14 Oct 2013 at 9:46

GoogleCodeExporter commented 8 years ago

Original comment by tarun.na...@3pillarglobal.com on 15 Oct 2013 at 12:11