2

When we send this request:

https://stackexchange.com/oauth/dialog/?client_id=`client_id`&scope=read_inbox%2cno_expiry%2cwrite_access%2cprivate_info&redirect_uri=https%3a%2f%2fstackexchange.com%2foauth%2flogin_success

the page gets redirected to http://stackexchange.com/

Again when we send this request to:

https://stackexchange.com/oauth/dialog/?client_id=`client_id`&scope=read_inbox%2cno_expiry%2cwrite_access%2cprivate_info&redirect_uri=https%3a%2f%2fstackexchange.com%2foauth%2flogin_success

then we get:

https://stackexchange.com/oauth/login_success#access_token=`access_token`

Isn't this wrong? We should be getting:

https://stackexchange.com/oauth/login_success#access_token=`access_token`

on the first request itself.

  • I'm voting to close this question as off-topic because there is Insufficient information to duplicate the problem. It needs an MCVE. – Brock Adams May 24 '16 at 22:02
  • 1
    Kindly ask for more information where it is not clear. This question was edited by stackapps.com/users/26088/%E1%94%95%E1%96%BA%E1%98%8E%E1%95%8A and favorited by some one also. – amit jha May 26 '16 at 6:54
  • Also reported less explicitly here: The Authentication Problem of WebAuthenticationBroke Classr in .NET 4.6 (seeing if someone reported the problem earlier for duping) – Tim Stone May 26 '16 at 11:21
  • 1
    @BrockAdams You can reproduce by trying to get an access token from the API console while not logged in, not sure if there's an earlier report of this or not – Tim Stone May 26 '16 at 11:33
  • @TimStone, I verified that I can authenticate just fine both from my applications and from the API livedocs. Also, the bug that you may be referencing always gave an error and seems to have been ninja-fixed in the last year anyway. The OP has failed to provide a recipe for this bug and maybe also omitted crucial error messages. – Brock Adams May 26 '16 at 20:36
  • The only other "First time" bugs were fixed long ago and not reoccurring now (in my spot checks). See stackapps.com/questions/3156/oauth-redirect-not-completing and linked question. – Brock Adams May 26 '16 at 20:42
  • 1
    @BrockAdams Were you already authenticated by the site? I can easily reproduce if I have to log into Google or the SE OpenID. The process takes you just to http://stackexchange.com/#, like is shown in the screenshot from the first linked question (here's my attempt) – Tim Stone May 26 '16 at 20:59
  • @TimStone, I tried it both ways (pre-authenticated and unauthenticated) x 3 different approaches (docs, implicit app, explicit app). I don't use Google however. Since you have a recipe to duplicate, maybe edit that into the question? – Brock Adams May 26 '16 at 21:05
  • @TimStone Okay, verified that stackapps.com/questions/6166/… is NOT fixed. This question is the exact same problem, minus the helpful error message that the duplicate question included. – Brock Adams May 26 '16 at 21:19

Browse other questions tagged .