garmin express token login to garmin connect

I can’t provide a fix but be aware that anytime you clear the browser cache you may have to then provide login credentials on many if not most apps, websites, etc.  At least that is my exp[erience.

Same here, SSO token does not work after update of Garmin Express. My browser settings automatically remove all saved data (including cookies), and logging in with the SSO token through Garmin Express always worked until this udate. This should be fixed by Garmin, seems their Garmin Express SSO method is not compatible with the web browser SSO functionality.

If your browser is set to consistently clear the cache and cookies then this is why it is prompting you to login again each time. When selecting the "Remember me" it is creating a cookie so any time that gets cleared from the browser you will need to enter your username and password again. 

Peter207Meter said:

Same here, SSO token

Thanks for the reply. I understand how cookies will remember login credentials. However, I am using these "auto-delete" browser settings for many years now for privacy reasons, and previous versions of Garmin Express app were able to automatically log me in using the SSO token. The updated Garmin Express is unable to do this, and I think the reason for this functionality break can be found in the analysis of topic starter 2987178 who discovered that the URL syntax changed. I will try to verify this later today by manually changing that URL syntax to reflect the previous syntax.

Same issue for me
I doubt it comes from cookies or browser cache : I have several devices belonging to different users defined in my Garmin express application..
Before the login to Garmin connect was done using the right Garmin account linked to each device.
And it would be nonsense to ask the system to "remember me" as each new connection may require another set of credentials. 

I’m seeing the same behavior after the newer Garmin Express updates. It does seem like the change from the old web_token URL to the sso/login?logintoken= flow altered how the authentication works. The previous method felt more like a direct token-based session, while the newer SSO flow appears to rely more on browser cookies and session persistence.

For users who automatically clear cookies (for privacy or security reasons), that would explain why the login isn’t retained anymore. Still, as others pointed out, older versions of Garmin Express handled this without requiring a manual login each time, so something definitely changed in the authentication implementation.

One thing I’m curious about: has anyone tested this with different browsers set as the default for Garmin Express (Chrome vs Edge vs Firefox)? If the SSO behavior is browser-dependent, it might explain why some users see it more than others.

Would be good if Garmin clarified whether this is an intentional change in the login flow or a regression introduced in the newer versions.

Do you have 2FA set up for your Garmin account? 

As a test, I just removed the latest 7.28 version and replaced it by 7.24. After installation, Garmin Express asks my login credentials. After adding my device I can click on the large Garmin Connect button, and it perfectly logs me in using SSO token, despite my browser settings which remove cookies consistently, and without any 2FA. So, to me this proves that the website itself still perfectly handles the SSO token login from 7.24 version, and it also proves that it is the latest 7.28 Garmin Express app on Windows changed in such a way that automatically login through that token does not work. If I may make a suggestion to the Garmin software tech teams, please have a detailed look, and if Garmin cares about a smooth user experience, please consider fixing this in a next release. I am not planning to store any credentials or cookies to fix this bug. At least, I am of the opinion that this is a bug as it is certainly not a feature ;-)

PS: I am using latest version of Firefox.

No I did not setup 2FA, please see my previous response for an additional test.

Why is this marked in green colour, suggesting that this is the solution? The solution is for the next version of Garmin Express to revert the SSO login call to your website, as described by topic starter. Having a SSO token that is unable to login does not make any sense, and storing cookies is NOT the solution. See my test as described below which verifies this.