Invoke-GetCCPCredential doesn't allow using all of the parameters available with Get-CCPCredential. In particular, the following parameters are ignored, but some are absolutely necessary in non-standard CCP setups.
These all are used to build the query (or supply a raw query in the case of Query) and would help to select the correct secret.
Safe
Folder
Object
UserName
Address
Database
PolicyID
Reason
Query
These are used to setup the connection and WebServiceName is absolutely necessary if the authentication method isn't setup with the default AIMService context.
ConnectionTimeout
WebServiceName
It would probably be good to just allow any parameters to be supplied as part of VaultParameters and let the Get-CCPCredential function tell the user if they have specified something that doesn't work.
I will try to get a PR submitted to cover this soon.
Invoke-GetCCPCredential doesn't allow using all of the parameters available with Get-CCPCredential. In particular, the following parameters are ignored, but some are absolutely necessary in non-standard CCP setups.
These all are used to build the query (or supply a raw query in the case of Query) and would help to select the correct secret. Safe Folder Object UserName Address Database PolicyID Reason Query
These are used to setup the connection and WebServiceName is absolutely necessary if the authentication method isn't setup with the default AIMService context. ConnectionTimeout WebServiceName
It would probably be good to just allow any parameters to be supplied as part of VaultParameters and let the Get-CCPCredential function tell the user if they have specified something that doesn't work.
I will try to get a PR submitted to cover this soon.