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.

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

Token Cache - Desktop - Linux Libsecret #477

Open
sreeise opened this issue May 27, 2024 · 3 comments
Open

Token Cache - Desktop - Linux Libsecret #477

sreeise opened this issue May 27, 2024 · 3 comments
Labels
Identity - OAuth OAuth crate issues
Milestone

Comments

@sreeise
Copy link
Owner

sreeise commented May 27, 2024

Implement Linux Libsecret (Desktop) as an option for token cache

@sreeise sreeise added the Identity - OAuth OAuth crate issues label May 27, 2024
@sreeise sreeise added this to the 2.2.0 milestone May 27, 2024
@sreeise sreeise mentioned this issue May 27, 2024
5 tasks
@kulst
Copy link

kulst commented Aug 18, 2024

Microsoft uses libsecret in their MSAL libraries to cache tokens in the Secret service. I would also consider using the Secret service here.
As far as I understand the Linux kernel's keyrings feature (not to be confused with gnome-keyring) does only provide a temporary solution to store authentication data in kernel memory. This means the data is gone after a reboot.

In comparison the Secret service (which libsecret is communicating with) and its implementations (like gnome-keyring) provide a way to permanently store authentication data in a encrypted file.

@sreeise sreeise changed the title Token Cache - Desktop - Linux KeyRing Token Cache - Desktop - Linux Libsecret Aug 20, 2024
@sreeise
Copy link
Owner Author

sreeise commented Aug 20, 2024

Microsoft uses libsecret in their MSAL libraries to cache tokens in the Secret service. I would also consider using the Secret service here. As far as I understand the Linux kernel's keyrings feature (not to be confused with gnome-keyring) does only provide a temporary solution to store authentication data in kernel memory. This means the data is gone after a reboot.

In comparison the Secret service (which libsecret is communicating with) and its implementations (like gnome-keyring) provide a way to permanently store authentication data in a encrypted file.

Thanks for the information on this. I updated the ticket to be for Libsecret instead of keyring.

I got the information for how MSAL handles it from looking at the code itself and I do see Libsecret now. But I also see stuff about Keyring. So im curios as to what you looked at or are using for this information?

@sreeise
Copy link
Owner Author

sreeise commented Aug 20, 2024

Microsoft uses libsecret in their MSAL libraries to cache tokens in the Secret service. I would also consider using the Secret service here. As far as I understand the Linux kernel's keyrings feature (not to be confused with gnome-keyring) does only provide a temporary solution to store authentication data in kernel memory. This means the data is gone after a reboot.
In comparison the Secret service (which libsecret is communicating with) and its implementations (like gnome-keyring) provide a way to permanently store authentication data in a encrypted file.

Thanks for the information on this. I updated the ticket to be for Libsecret instead of keyring.

I got the information for how MSAL handles it from looking at the code itself and I do see Libsecret now. But I also see stuff about Keyring. So im curios as to what you looked at or are using for this information?

As soon as I posted that I went and looked at the docs that I posted previously and saw that it said

The token cache is stored in the a wallet such as Gnome Keyring or KWallet using LibSecret.

🤣

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Identity - OAuth OAuth crate issues
Projects
Status: No status
Development

No branches or pull requests

2 participants