Skip to main content
Solved

Oauth token 404 response

D
Forum|alt.badge.img+4

I am setting up oAuth flow in postman and all works ok until it calls the token URL at which point it fails with a 404 as per the below. If anyone has some ideas on this help would be much appreciated:

 

▶POST https://www.strava.com/api/v3/token
 137 ms
  • ▶Network
    ▶Request Headers
    Content-Type: application/x-www-form-urlencoded
    Authorization: Basic MTEyOTM1OmIyOTUxMjZiYmIwYTBkZThkNzVjNDdkYWMwZDc3NDJkYTI1ZWIzZDY=
    User-Agent: PostmanRuntime/7.32.3
    Accept: */*
    Cache-Control: no-cache
    Postman-Token: 5338b39b-26c7-4e29-8522-37083712d01d
    Host: www.strava.com
    Accept-Encoding: gzip, deflate, br
    Connection: keep-alive
    Content-Length: 133
    Cookie: _strava4_session=oi9vk4mpurrq5ere7c9msr25p75menc6
    • ▶Request Body
      1.  grant_type: "authorization_code"
      2.  code: "e2632985384fd78ff6d482d42fedb3cfcb20cf7d"
      3.  redirect_uri: "https://oauth.pstmn.io/v1/callback"
        ▶Response Headers
        Content-Type: application/json; charset=utf-8
        Transfer-Encoding: chunked
        Connection: keep-alive
        Date: Wed, 30 Aug 2023 10:06:54 GMT
        Via: 1.1 linkerd, 1.1 linkerd, 1.1 b66a7470c341bb8edfe0c35c17d6e508.cloudfront.net (CloudFront)
        Vary: Accept, Origin
        Pragma: no-cache
        Server: nginx/1.21.3
        Status: 404 Not Found
        Expires: Sat, 01 Jan 2000 00:00:00 GMT
        X-Request-Id: 2d3b4acd-92e4-4ae0-b73b-998df6d7566e
        Cache-Control: no-store
        Referrer-Policy: strict-origin-when-cross-origin
        X-Frame-Options: DENY
        Content-Encoding: gzip
        X-XSS-Protection: 1; mode=block
        X-Download-Options: noopen
        X-Content-Type-Options: nosniff
        X-Permitted-Cross-Domain-Policies: none
        X-Cache: Error from cloudfront
        X-Amz-Cf-Pop: LHR61-P6
        X-Amz-Cf-Id: yxmqCjPngWgMsfn1LESnVmE6P06ov6HJP6ezzQb47QpanmmRxZVjjQ==
        ▶Response Body
        {"message":"Record Not Found","errors":[{"resource":"resource","field":"path","code":"invalid"}]}
      4.  
      5.  

Best answer by DennisParker

Correcting this reply - I see that your are correct - investigating - thanks for the pointer

 

The client_id and client_secret are passed to the authorize call which returns successfully with the code that you see in the request body. The token call does not take the client_id and client_secret but rather the code that is generated from the authorize call which is returned after the user has successfully entered a userid and password based on the oAuth challenge. 

 

 

 

View original
Did this topic help you find an answer to your question?

6 replies

D
Forum|alt.badge.img+4
  • DennisParker
  • Author
  • Hub Rookie
  • 4 replies
  • August 30, 2023

URL verified and problem still exists. Any help appreciated

Jan_Mantau
Superuser
Forum|alt.badge.img+26
  • Jan_Mantau
  • Superuser
  • 948 replies
  • August 31, 2023

The correct URL for getting the tokens is https://www.strava.com/api/v3/oauth/token

D
Forum|alt.badge.img+4
  • DennisParker
  • Author
  • Hub Rookie
  • 4 replies
  • August 31, 2023

Thanks Jan_Mantau - I changed to your suggested URL and here is the result. Error code has changes from a 403 to a 400 - but still not working. I have verfied that the client-id and secret are correct and this works in the playground but not in postman using the oAuth flow

 

 

Jan_Mantau
Superuser
Forum|alt.badge.img+26
  • Jan_Mantau
  • Superuser
  • 948 replies
  • August 31, 2023

Your client_id and client_secret are missing from the request body.

D
Forum|alt.badge.img+4
  • DennisParker
  • Author
  • Hub Rookie
  • 4 replies
  • Answer
  • August 31, 2023

Correcting this reply - I see that your are correct - investigating - thanks for the pointer

 

The client_id and client_secret are passed to the authorize call which returns successfully with the code that you see in the request body. The token call does not take the client_id and client_secret but rather the code that is generated from the authorize call which is returned after the user has successfully entered a userid and password based on the oAuth challenge. 

 

 

 

D
Forum|alt.badge.img+4
  • DennisParker
  • Author
  • Hub Rookie
  • 4 replies
  • August 31, 2023

This solved the problem - please note in postman you need to do additional advanced configuration in hte oAuth config to pass the client_id and client_scret to the token call. You can see a screen shot of that configuration below. This is interesting as this data is already passed to the authorize api call and I am not sure why the token call needs this data again. However once you configure these the oAuth calls will work correctly

Thanks Jan_Mantau for helping me through this investigation

Jan_Mantau
1 person likes this
  • Jan_Mantau
    Jan_Mantau

Reply


Most helpful members this week

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept, you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings