You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The key {d9046a7e-96ef-415f-833c-XXXXX243326} was not found in the key ring. For more information go to http://aka.ms/dataprotectionwarning
Expected Result
User able to login to the Bitwarden via SSO
Actual Result
New joined user not able to login to the Bitwarden, and received below error
The key {d9046a7e-96ef-415f-833c-XXXXX243326} was not found in the key ring. For more information go to http://aka.ms/dataprotectionwarning
Screenshots or Videos
Additional Context
Previously user able to login, within last 2 weeks new user invited into Bitwarden received the reported issue.
Build Version
2023.2.1 and 2023.5.1
Environment
Self-Hosted
Environment Details
Environment : EKS
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.
The text was updated successfully, but these errors were encountered:
Steps To Reproduce
Expected Result
User able to login to the Bitwarden via SSO
Actual Result
New joined user not able to login to the Bitwarden, and received below error
Screenshots or Videos
Additional Context
Previously user able to login, within last 2 weeks new user invited into Bitwarden received the reported issue.
Build Version
2023.2.1 and 2023.5.1
Environment
Self-Hosted
Environment Details
Environment : EKS
Issue Tracking Info
The text was updated successfully, but these errors were encountered: