[Windows] Custom persistence flag for Secrets SDK

[traeok]

Is your feature or enhancement request related to a problem or limitation? Please describe

Some corporate environments encounter errors when using the CRED_PERSIST_ENTERPRISE persistence level when storing secure credentials on Windows.

Describe your enhancement idea

Allow the user to pass a custom persistence level to the Secrets SDK that, when provided, is used instead of CRED_PERSIST_ENTERPRISE. We should fallback to CRED_PERSIST_ENTERPRISE to preserve existing capabilities.

Describe alternatives you've considered

N/A

Provide any additional context

Implementing this will resolve #2458

[github-actions]

Thank you for raising this enhancement request.
The community has 90 days to vote on it.
If the enhancement receives at least 5 upvotes, it is added to our development backlog.
If it receives fewer votes, the issue is closed.

[JWaters02]

The additional ehancement here is that it gives orgs more control of how much persistence they want to allow credentials to be stored at.

Currently there are only two "extremes" - autoStore: false (re-input creds every session which can be a huge thorn for dev workflow, but does no credential storage), and enterprise level credential storage, which is where the user credentials is synced for that logged in user across the network so their credentials can work from any corporate windows device if they logged in on it (credentials are stored permanently).

Allowing the other two flags (CRED_PERSIST_SESSION and CRED_PERSIST_LOCAL_MACHINE) allows for a couple options in the middle where credentials are wiped by the system for certain circumstances.

[zFernand0]

We should look into making this a bit more flexible in case people need to customize the CredentialManager a bit more. 😋
Source: https://learn.microsoft.com/en-us/windows/win32/api/wincred/ns-wincred-credentiala#members