Securely caching credentials

[ThePoShWolf]

@mattmcnabb What are your thoughts on securely caching credentials passed to Connect-OneLogin? That way one could connect once, have the module cache the Client ID and secret and then every future time the module is loaded re-connect without having to pass credentials.

It is possible to do so with writing secure strings somewhere (file, registry, etc), or, on Windows, read/write from the credential manager.

[mattmcnabb]

@ThePoShWolf I'm not sure about that one. There are already ways to manage credentials in PowerShell such as the ones you've mentioned, and there are new ones coming down the pipe with credential managers in PowerShell 7. I see at least two issues with writing credential management in utility modules like this:

1. Duplicated effort - credential management is a common enough need that we could essentially be including the same type of credential support in many different modules.

2. Security Risk - adding credential management capability to a module introduces a liability and that liability is probably better suited to a dedicated module or feature. I'm not ready to sign that contract with users of this module 🤣

I'm ok with letting credential managers do credential management, and using those features to pass credentials directly to module commands.

[ThePoShWolf]

Instead of implementing this in the module itself, I would like to instead document usage of credential managers to cache the credentials.