Unable to edit multiple sessions in bulk, credentials not saved #2

New issue

Closed

opened 2026-04-14 13:06:32 +02:00 by tux · 2 comments

tux commented

2026-04-14 13:06:32 +02:00

Owner

How to replicate:

Right-click on a folder containing multiple sessions.
"Edit Sessions..."
Fill in username, password, jump-host, highlight profile

The log gets filled with

2026-04-14T10:55:50.742540Z ERROR shellstation_lib::commands::session: bulk keychain store failed: Failed to store credential: Platform secure storage failure: Windows error code 8 session_id=xxxxxxxxxxxxxxxxxxxx

for each session.

Upon checking a single session from the folder, only the username seems to have been set, no entry for jumphost or hightlight profile.
When trying to connect, it fails, on the remote system log one can see "fail reason: emptyPassword".
When trying to edit the single session and entering the password, upon saving the same error can be seen in the log.

When checking the MS Windows credentials manager, lots of shellstation entries can be seen, but as its only the session id its hard to verify, if the problematic is upon them.

Might be related to it being a company workstation with GPOs.

How to replicate: - Right-click on a folder containing multiple sessions. - "Edit Sessions..." - Fill in username, password, jump-host, highlight profile The log gets filled with `2026-04-14T10:55:50.742540Z ERROR shellstation_lib::commands::session: bulk keychain store failed: Failed to store credential: Platform secure storage failure: Windows error code 8 session_id=xxxxxxxxxxxxxxxxxxxx` for each session. Upon checking a single session from the folder, only the username seems to have been set, no entry for jumphost or hightlight profile. When trying to connect, it fails, on the remote system log one can see "fail reason: emptyPassword". When trying to edit the single session and entering the password, upon saving the same error can be seen in the log. When checking the MS Windows credentials manager, lots of shellstation entries can be seen, but as its only the session id its hard to verify, if the problematic is upon them. Might be related to it being a company workstation with GPOs.

tux commented

2026-04-14 13:15:49 +02:00

Author

Owner

Update:
The actual source of the issue was found.
The windows credential store has only a limited capacity, error code 8 means, out of storage.
Attempting to store more than 1000 credentials for sessions hit the limit.
Upon deleting a couple of credentials, storing a limited set of session credentials then worked.

Update: The actual source of the issue was found. The windows credential store has only a limited capacity, error code 8 means, out of storage. Attempting to store more than 1000 credentials for sessions hit the limit. Upon deleting a couple of credentials, storing a limited set of session credentials then worked.

tux commented

2026-04-14 16:33:50 +02:00

Author

Owner

Fixed in #1e5f81e249, in release 0.9.4

Fixed in #1e5f81e2490f3f8c8c13818418928701725a8932, in [release 0.9.4](https://git.fiedler.live/tux/shellstation/src/tag/v0.9.4)