SSO login returns token missing in keyring error

### Steps To Reproduce

1. Go to 'bitwarden.yourdomain.com
2. enter login info for you org
3. Select sign in with SSO
4. Enter Org ID
5.
6. Error returns

### Expected Result

SSO logs in user and requests master password

### Actual Result

Error
There was an unexpected error during single sign-on.

The key {4991ac6e-606d-451d-ae14-72ddb5ddbc48} was not found in the key ring. For more information go to http://aka.ms/dataprotectionwarning

### Screenshots or Videos

_No response_

### Additional Context

Works for most users, specific to a handful with no discernable similarities.

Users that fail SSO are still able to login with regular username/password.

### Githash Version

{"version":"2023.4.3","gitHash":"8d9ca424-dirty","server":null,"environment":

### Environment Details

Kubernetes deployment with BW_ENABLE_SSO set to True

### Database Image

_No response_

### Issue-Link

https://github.com/bitwarden/server/issues/2480

### Issue Tracking Info

- [X] 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.

Start by reviewing the SSO flow and the related issue at bitwarden/server#2480, then reproduce the key-ring failure in the Kubernetes deployment with BW_ENABLE_SSO enabled. Done means identifying why affected SSO users cannot retrieve the key, restoring SSO login while preserving regular username/password login, and verifying the result for the reported version context.

Written by the indexing model from the issue text.