o.sl.ij.config.global.credentials.CredentialsException: Could not load token or login/password credentials for connection: XXXX
at o.sl.ij.config.global.credentials.CredentialsService.readCredentials(CredentialsService.kt:63)
at o.sl.ij.config.global.credentials.CredentialsService.getCredentials$lambda$0(CredentialsService.kt:43)
at o.sl.ij.util.ThreadUtilsKt.computeOnPooledThread$lambda$5(ThreadUtils.kt:72)
at c.ij.oa.ap.impl.ApplicationImpl$5.call(ApplicationImpl.java:356)
at c.ij.util.concurrency.ContextCallable.lambda$call$1(ContextCallable.java:86)
at c.ij.util.concurrency.ContextCallable.call(ContextCallable.java:95)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
at c.ij.util.concurrency.ChildContext$runInChildContext$1.invoke(propagation.kt:167)
at c.ij.util.concurrency.ChildContext$runInChildContext$1.invoke(propagation.kt:167)
at c.ij.util.concurrency.ChildContext.runInChildContext(propagation.kt:173)
at c.ij.util.concurrency.ChildContext.runInChildContext(propagation.kt:167)
at c.ij.util.concurrency.ContextRunnable.run(ContextRunnable.java:27)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:735)
at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:732)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:400)
at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1.run(Executors.java:732)
at java.base/java.lang.Thread.run(Thread.java:1583)
Thanks for reaching out to us. There was a migration of sensitive data storage in IntelliJ recently. That includes tokens for connection. So I guess something went wrong with it. Can you please confirm:
You are not able to edit old connection but are you able to create a new one instead and authenticate it? (Because if a new token can not be saved, that’s a bigger issue)
So if you are able to create a new connection, the workaround would be to recreate your connections manually. Migration clears the old storage so unless you are able to edit the connection it’s the only way.
If recreating the connections doesn’t work, then please give send us verbose logs so that we can understand what’s happening. The sensitive data storage that we are using now is platform-specific. For Windows it should just create a file in KeePass format so you can also take a look at IntelliJ logs and see if there are some problems with that. (For example for our linux testing containers we had to add some utilities to the image for it to work but we normally expect them to be in place on user machines since IntelliJ is relying on them.)
Another workaround is to do as IntelliJ page on sensetive data persistance says:
Users can override the default behavior in Settings | Appearance & Behavior | System Settings | Passwords.
There might be another way of storing sensitive data. If you can not create a new connection, then please try please change this setting first and then try again. (Might require IDE restart.)
In case if nothing works potential workaround would be to roll back to older version of pluigin with old token management (11.1) but keep in mind that stored passwords were already wiped from storage so you will have to re-authenticate in this case anyway.
Creating a new connection while not deleting the existing one was possible but didn’t work. I was unable to define the project binding. Press on the “Search in list” button to find the project key was displaying an error message popup telling it can not load token credential. (Verbose logs shown nothing more than file analysis traces and the error message seen on the popup, no traceback nor previous step leading to this error. Unfortunately, I’ve lost my clipboard content at some point with the exact error message.)
Clearing all connections, restart the IDE, then create the connection again did work and I am able to set the binding and use it.
Unfortunately, we can’t fully control this as we rely on IntelliJ that, in turn, relies on 3rd party means for the storage. That are platform-specific on top of that. Issues with the migration are inevitable. But your experience will help any further users encountering the same issue.