Configuration Element of type SecureString not passing to Workflow?

[Czernobog]

Hi,

for my scripting needs I have defined a set of Configuration Elements, which allows easy access to some common variables, like SMTP information. I have also created a new attribute "Password" of the type SecureString, which, paired with a string attribute "Username" is used to run test scripts with the VM Guest Operations Package. The problem is, when I try to bind the attribute value of "Password" to an attribute in the workflow I get a validation error "configuration was not set for this attribute". The "Username" value is also passed down to the attribute from the configuration element without problems.

Is it not possible to use a configuration element of the type SecureString in you workflows?

[qc4vmware]

Yes this should work just fine.  If you can give some more detail or upload a sample of your workflow it might shed some light on whats breaking.

[Dan_Linsley]

You have done it correctly, but vCO is warning you that the config element needs to have a value.

Setting a non empty value in your "Password" attribute will resolve this.

[Burke-]

As Paul & Dan have indicated, this should work - we use this method, and teach it, frequently. Have you gotten this resolved? Can this thread be marked as answered?