Fixed
Project:
Strava API
Version:
3.0.0-alpha1
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
17 Oct 2018 at 21:01 UTC
Updated:
15 Jul 2026 at 12:24 UTC
Jump to comment: Most recent
Implement the new authentication and scope changes as described here: https://developers.strava.com/docs/oauth-updates/
Important Dates
October 15, 2018
New OAuth endpoints for acquiring short-lived access tokens and refresh tokens are available. New scopes are available.
January 15, 2019
Email address is no longer part of the profile:read_all scope and is removed from the athlete model.
October 15, 2019
Forever tokens are rejected by the server. Old OAuth endpoints for obtaining forever tokens are removed.
Comments
Comment #2
basvredelingComment #3
basvredelingStarting tomorrow, the email address will be removed from the athlete data. So onwards it will be problematic trying to couple Drupal users to Strava athletes based on email. This issue urgently needs some attention.
Problem 1:
strava_user_login() will no longer work.
Problem 2:
The AthleteUserHandler no longer works as designed, especially: userExists() & userCreate().
Problem 3:
I think the "write" scope is already invalid.
Problem 4:
The Athlete and AthleteInterface needs to be reworked (is the email property still valid?).
Problem 5:
The StravaPHP library is not up-to-date.
Problem 6:
UserManager class looks obsolete.
Comment #4
basvredelingI've added some partial work on the issues mentioned in comment #3 in the current 1.x-dev branch.
Coupling a Strava profile / athlete to a Drupal user is off the table for now, since we no longer can connect those entities via an email address.
Comment #5
basvredelingProblem 3 and 5 mentioned in #3 have been addressed.
Comment #6
basvredelingContributions appreciated
Comment #7
f0ns commentedParts of this are resolved in 3.x:
Still open:
Moving this to 3.x, remaining work (refresh token support first) will land here.
Comment #8
f0ns commentedComment #9
markconroy commentedI've created 3 separate issues for each of these, which might make it easier to get people to work on each.
Will we close this issue in favour of those 3 issues?
Comment #10
f0ns commentedGood idea, closing this down.
Thank you for making the splits. Should have done that right away now that I think about it.
Comment #11
f0ns commented