Currently, it is possible to configure the location of the auth config file in the default keychain, but only if there is not already a config file at the default path. Furthermore, the name of the file (config.json) is hard-coded and cannot be overridden. It would be helpful to support passing an arbitrary path to credentials to be used, perhaps as part of a multi-keychain. This would be straightforward to implement in consume in the same manner as other alternative keychain implementations, such as github and k8schain.