Prusa Connect periodically fails with "missing or invalid token"

[quintesse]

Description of the bug

Even with the latest version 2.8.1 I get continuous "Missing or invalid security token" errors in the Prusa Connect tab.

This issue is similar but not exactly the same as #13137, I'm not getting blank pages anymore, but just a "working" page that doesn't let me do anything because it's missing the security token.

I think it would be very useful to have a way to force PrusaSlicer to re-authenticate without having to restart (which forces me to save ephemeral changes to a scrap project just so I don't lose those changes when restarting and then having to delete that file. It's a bit of a nuisance)

Project file & How to reproduce

Can't give an exact foolproof way to reproduce, but I think it's simply letting PrusaSlicer open for a long time.
If "enough" time has passed this problem will occur (and there doesn't seem to be a work-around except restarting PrusaSlicer).

Checklist of files included above

• Project file
• Screenshot

Version of PrusaSlicer

1.8.1

Operating system

Windows 11 Pro

Printer model

XL 2 head

[m10d]

While the result is similar (must re-log in), your missing or invalid token error does sound different than the "failed to connect" as seen in #13137 (comment) ; no comment on if they share a root cause.

Can you please clarify a few things from your OP: (also, edit your title so it doesn't look like a dup of 13137)

• does re-starting the app result in you logged in (eg is this something like an oauth refresh access/bearer token issue, not an actual logout)? Or do you have to fully re-log-in?
• while you're experiencing this error, does anything on the Connect tab refresh (or is it just displayed, but staying in a stale state? If it's refreshing, that would imply multiple paths to handle the auth refresh (odd), or a security issue).

Note your symptoms sound a lot like a failure on some paths to request a new access token with (assuming restarting the app DOES fix the issue, no password required) the refresh token the app stores. access tokens are ~short lived, they're supposed to expire quickly as part of their design. A new one is obtained behind the scenes by whatever app, using the refresh-token. At least that's OAUTH2, if you're curious)

[quintesse]

@m10d it does indeed seem more like a refresh issue, given the fact that it only happens after a certain time has passed and that, as you surmised, the app reconnects without needing a login after being restarted.

As to the second point, I did not pay 100% attention, will try to reproduce now and take a closer look. But as far as I can recall the page shows stale information. As you can see from the screenshot it actually showed me as still being logged in (both in the app itself as in the embedded Prusa Connect page). I could also change tabs. But many (all?) actions caused an error popup.

I'm somewhat familiar with OAuth2 and the idea of refresh tokens so it could indeed be that the refresh is not being handled correctly. I don't know how short-lived the access tokens are. If they are in the minutes then it could mean that the refresh normally works but sometimes fails (and then doesn't retry but enters in a failed state that it can't get out of) or the tokens are somewhat longer-lived, let's say an hour, which could possibly mean that the refresh doesn't work at all (at least in my case).

[michael-gillett]

I'm running into the same issue as @quintesse. I've only seen it happen if I leave Prusa Slicer open for a long time, but minimized/ in the background. The Prusa Connect tab still displays the web page skeleton with previous data and the error toast in the bottom right about missing security token.

If I quit and reopen the slicer it fixes the problem when revisiting the Prusa Connect tab. I feel like I fixed it once, without quitting, by clicking into Username > User Teams in the top right, but I can't reproduce this time.

Version 2.8.1+MacOS-arm64

[quintesse]

I was able to reproduce it by switching back to any other tab and leaving it open on the desktop. When I left it on the Prusa Connect tab it didn't seem to happen. But perhaps minimizing would have worked as well as @michael-gillett found out.
I can still move to different tabs and some will show some information but most will just pop up a bunch of extra errors.
I once tried to make a change (set a hotend temperature) and after a couple of minutes the tab went completely blank with just a single "Connection Failed. Something went wrong" message in the center. Logging out and in again make things work, so does restarting.
(NB I really think we need a way to force a refresh, it's a web page after all :-) )

[bryn51]

I also observe this issue occurring. The Prusa Connect login button at top right of Prusa Slicer screen shows user is logged in, but when Prusa Connect button is clicked, the details are inaccurate. When "Set Ready" is clicked on a printer, nothing happens, or sometimes it says "Missing or invalid security token". What ought to happen is that Prusa Slicer keeps the login status "alive" ongoing, and when "Prusa Connect" button is clicked, if necessary the prusa connection login status is refreshed and the contents of the screen brought up to date immediately.

[a1athrop]

I am having this same issue.

[justinpierson]

Same issue here, if I leave PrusaSlicer open for a while and then try to access the printers files I get the error "Invalid Security Token" I can still send prints to it, I just cannot do anything with the printer.

[MichaelEhrlichman]

Same issue here.

[Jan-Soustruznik]

It seams similar to #13439

[quintesse]

It seams similar to #13439

Actually that one seems more similar to a bug that was supposedly fixed in 1.8.1, namely #13137

[feesta]

I have also been having this problem on 1.8.1 running on MacOS. I tried running from the command line so logs show up. This error popped up after about 37 minutes of PrusaSlicer sitting in the background which corresponds to seeing 'Missing or invalid security token' notifications in the app:

[2024-11-08 10:45:52.576715] [0x00000001e9038f40] [error] Failed communication with Prusa Account: 0x60001db75c48 action failed (400): {
"message": "key parameter is invalid"
}