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

issues with authentication process #31

Closed
mgnwong opened this issue Apr 18, 2019 · 9 comments
Closed

issues with authentication process #31

mgnwong opened this issue Apr 18, 2019 · 9 comments

Comments

@mgnwong
Copy link

mgnwong commented Apr 18, 2019

Authorize function is returning the error "Authentication failed - please check your credentials" because the login form needs a csrf value, apparently. Has anyone gone over this?

@fulmar2
Copy link

fulmar2 commented Apr 18, 2019

I am having this issue as well - since about 2 or 3 days ago.

@JLTRY
Copy link

JLTRY commented Apr 20, 2019

same issue for me let me know if any progress

@Yngve0
Copy link

Yngve0 commented Apr 21, 2019

It seems like they not only added a CSRF-value, but also some other changes in the SSO-form.

Seems like Garmin dont see the value of this opensource-addOns. :(

@cabby26
Copy link

cabby26 commented Apr 22, 2019

same Problem

@DaveWilcock
Copy link
Member

DaveWilcock commented Apr 24, 2019

Thanks all. I'm currently on anual leave, but should be able to look at this soon. I'll need to decompose the Garmin login screens and see if there's anything we can do here. However, the mention of CSRF doesn't fill me with hope, especially if they've done it right.

@raven-ie
Copy link

@dawguk the referenced issued have a working fix in place.

@DaveWilcock
Copy link
Member

Yep, I posted a request to take a look at their PR and see if we can do the same thing. I'll have a play later ...

JLTRY added a commit to JLTRY/php-garmin-connect that referenced this issue Apr 27, 2019
JLTRY pushed a commit to JLTRY/php-garmin-connect that referenced this issue Apr 27, 2019
@DaveWilcock
Copy link
Member

This is now resolved in pull request #34

@DaveWilcock
Copy link
Member

Forgot to mention, thanks to @JLTRY for the triggerig of this fix, I got my lazy-self back to the computer to resolve.

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

No branches or pull requests

7 participants