In memory cache of MSAL tokens for Non-GUI Linux Scenarios

[bpkroth]

Feature description

Some organizations now require an MSAL token for authentication to git repositories instead of SSH.

However, the current ecosystem doesn't allow for an in memory cache of the MSAL token for use by multiple git invocations (e.g., via git credential store).

Please consider integration here to allow a more secure but also user friendly deployment, similar to what one has with ssh-agent for instance.

[sam-mfb]

As explained in 1549 this is, unfortunately, not something in gcm's control. The plaintext storage is created and controlled by the MSAL library, so no matter what gcm does that plaintext file is still going to be created until the MSAL library changes.

In terms of having a solution similar to ssh-agent that would allow forwarding requests from linux to gcm on another host via a socket or the like, there is a discussion item on that here