Related

garmin express token login to garmin connect

2987178

After updating Garmin Express I cannot auto login to Garmin Connect. I just get prompted for login to Garmin Connect. I can of course click remember me but If I clear my browser cache I need to log in again.

I tried to uninstall and install an older version of Garmin Express. Garmin Express 7.24.0 work fine by using https://connect.garmin.com/dashboard?web_token=xxxxx and logs me into my account. Later versions use https://sso.garmin.com/sso/login?logintoken=xxxxx and that just gives me the sign in screen

Anyway to fix this?

  • 0

    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.

  • 0

    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.

  • 0

    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
  • 0 in reply to Garmin - SP

    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.