Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Strava, Runalyze: Runkeeper login with Google: disallowed_useragent #791

Closed
gerhardol opened this issue May 25, 2019 · 1 comment · Fixed by #1025
Closed

Strava, Runalyze: Runkeeper login with Google: disallowed_useragent #791

gerhardol opened this issue May 25, 2019 · 1 comment · Fixed by #1025

Comments

@gerhardol
Copy link
Collaborator

Login to Strava, Runalyze or RunKeeper using Google fails with disallowed_useragent
It is possible to login to the services using direct login or Facebook.

Note: This will be seen when updating to 2.0.0.5 for Strava, as the authentication is changed (Strava will drop the old auth in October). So this is not a problem with 2.0.0.5

Strava will require a redesign, to auth in a different way. Strava has some hints for this.
For Runalyze, I am not aware of how this can be done, direct login recommended.
RunKeeper has disallowed the open API and will likely shut it down anyway so nothing should be done. (To be removed in #701)

@c5c86a
Copy link

c5c86a commented Sep 11, 2020

A workaround for runalyze if you logged in from a browser with SSO is to change password and the use along with your username as the credentials instead of doing SSO.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants