Closed ccamacho1966 closed 1 year ago
This can be made to work with -BypassValidation ... but that's a rather heavy hammer to use for a provider name that Venafi accepts as valid.
PS> Set-TppAttribute -Path $cert.Path -Attribute @{"Custom ID field"="$($anIdentity.ID)"} -BypassValidation
Test-TppIdentity : Cannot validate argument on parameter 'ID'. 'AD+AD xyz.net:54000000000000000000000000079006' is not a valid Prefixed
Universal Id format. See https://docs.venafi.com/Docs/current/TopNav/Content/SDK/WebSDK/r-SDK-IdentityInformation.php.
At C:\Program Files\WindowsPowerShell\Modules\VenafiPS\5.4.1\Public\Set-TppAttribute.ps1:162 char:49
+ ... thisValue | Test-TppIdentity -ExistOnly -VenafiSession $VenafiSession ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (AD+AD xyz.net:5...000000000079006:String) [Test-TppIdentity], ParameterBindingValidationExce
ption
+ FullyQualifiedErrorId : ParameterArgumentValidationError,Test-TppIdentity
Is that a real AD/friendly name with a space in it? I didn't think that was permitted.
resolved by #206
Environment
Steps to reproduce
Expected behavior
Happily accepting my horrible identity provider name "AD xyz.net" since it works fine (even if it is ugly).