Hey there,

I've been trying to utilise the persistent/on disk cache feature of the azidentity package.

I'm unclear if my problems are a result of misunderstanding what is expected of a persistent cache, or if this is a problem with the package itself, but on Linux (I'm developing on Linux Mint) using the persistent cache retains the relevant tokens between different executions of the program, but does not persist across reboots.

Looking at the Linux implementation, a comment notes:

// Attempt to link a persistent keyring to the user keyring. This keyring is persistent in that
// its linked keys survive all the user's login sessions being deleted but like all user keys,
// they exist only in memory and are therefore lost on system shutdown. If the attempt fails
// (some systems don't support persistent keyrings) continue with the user keyring.

And looking at it, this is just a result of how keyctl on Linux works.

The token caching documentation lists Keychain and DPAPI as being the solutions for MacOS and Windows. I'm not set up for development on either of those operating systems, but my reading suggests that the persistent token cache using those implementations is more likely to persist across a reboot.

I guess my question is: Is the persistent token cache intended to persist across reboots?

If it is, then the Linux implementation does not achieve that.
If not, it could be useful to clarify the intent in the token caching documentation.