Windows client refuses to login with organization ssh-key

[kaasszje]

Steps To Reproduce

I'm using the windows bitwarden client (version 2025.1.3)
I create a new ssh-key, copy the public key to my server.

When I login with this key this works.
I authorize the use of the key and get logged in.

After this I logout, move the key to my organization.
Sync the client, ssh-add -l shows the key.
Now when I try to log in, I get the authorize prompt again.
But when I click on authorize, the cli gives this message:
sign_and_send_pubkey: signing failed for ED25519 "Bitwarden-test" from agent: agent refused operation

Expected Result

Expected result was a succesful login.

Actual Result

Actual result: sign_and_send_pubkey: signing failed for ED25519 "Bitwarden-test" from agent: agent refused operation
And I'm not logged in, but get a disconnect

Screenshots or Videos

Additional Context

No response

Operating System

Windows

Operating System Version

Windows Server 2022

Installation method

Direct Download (from bitwarden.com)

Build Version

2025.1.3

Issue Tracking Info

• I understand that work is tracked outside of GitHub. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

[bitwarden-bot]

Thank you for reporting this issue! We've added this to our internal tracking system.
ID: PM-17746

[cksapp]

Just commented on #13164 based on this similar concern.

Afaik this is intentionally set at this time to prevent SSH keys stored on collections.