Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Error message when token cache persistence fails could be more descriptive #4493

Closed
christothes opened this issue Jan 10, 2024 · 0 comments · Fixed by #4497
Closed

Error message when token cache persistence fails could be more descriptive #4493

christothes opened this issue Jan 10, 2024 · 0 comments · Fixed by #4497
Assignees
@bgavrilMS
Labels
bug cache-extensions P2 public-client
Milestone
4.59.0

Comments

@christothes
Copy link

This error

"Persistence check failed. Data was written but it could not be read. Possible cause: on Linux, LibSecret is installed but D-Bus isn't running because it cannot be started over SSH."

could be more descriptive and accurate as it applies to various platforms. In addition the exception behavior is inconsistent (on Linux we don't throw exceptions, we just log them).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bgavrilMS bgavrilMS

Labels
bug cache-extensions P2 public-client
Projects
MSAL Customer Trust / QM
Archived in project
Milestone
4.59.0
3 participants
@christothes @bgavrilMS @pmaytak