omniauth / omniauth-venmo Goto Github PK

Hey,
The redirct url path (user_omniauth_authorize_path) has changed so the redirect is no longer (https://api.venmo.com/oauth/) but (https://api.venmo.com/v1/oauth/), the v1 has been added. As such I can longer authenticate. Can you please advise.

Is it possible that the v1 addition in your strategy file is not respected by rails 4 or oauth2 ?

Cheers

On 11/8 Venmo will be deploying changes to how they grant long-lived tokens to API consumers. This does not affect tokens that have already been granted.

• Tokens issued through the server-side authentication flow will no longer be non-expiring. These tokens expire after 60 days.
• To refresh these long-lived tokens, clients can exchange a refresh token (the refresh_token field included in the server-side authentication response) for a new access_token, refresh_token pair. Note that exchanging a refresh token for new tokens must be done only after the associated access token has expired.
• An expires_in field will now be included in the server-side authentication response. The value is in seconds.

Old Response:

{
"access_token": ACCESS_TOKEN, 
"user":  {...}
}

New Response:

{
"access_token": ACCESS_TOKEN,
"user": {...},
"refresh_token": REFRESH_TOKEN,
"expires_in": 5184000
}

After the token has expired, you need to POST to /oauth/access_token with REFRESH_TOKEN, CLIENT_ID, CLIENT_SECRET and receive a new access token, refresh token, and time to expiration.

Hi, I am able to pull up the venmo login but only if I get rid of the brackets on the ENV['client_id'] and secret, then - I get

{"error": {"message": "Missing argument: client_id.", "code": 241}} on the callback, and it endlessly repeats itself...

solved rails 4.0.x issue...
Use with 3.2.

Additionally, there might be a problem with the scopes. It is currently only passing the default access profile argument even with others specified.

Thanks again!