Get-VstsEndpoint returning masked credentials about azure-pipelines-task-lib

[bryanmacfarlane]

That is not how it gets deserialized. It doesn't yield that.

You are logging the json. It's the log that's masking the secret.

[dotnetnate]

That's not the only way it was verified. I have a user name and password variable, which are originally assigned from task inputs. Everything works correctly when that takes place. If I assign the contents of username/password from the endpoint to those variables the connection fails. Moreover, calling Write-Host on each variable with the input assignment shows the expected contents in the lof, whereas when re-assigning from the endpoint, it doesn't. If it was securestring this would arguably make sense, but as it's not, it doesn't.

[ericsciple]

auth.parameters is a string->string dictionary

dumping the endpoint to a file may help illuminate what is going on. when using convertto-json, you may need to specify a higher depth, e.g. -depth 99.

the secrets in the output logs are scrubbed by the logger - i.e. replaced with "********"