In custom properties at project level I observed that when I provide the value for the Password as a variable, it shows as hidden (****) However when I run the request using the variable I could cle...
Ok, in my case and I am sure in lot of other cases, one needs to provide password in soap header where it becomes visible. By having it as custom property makes it easy to maintain for entire project. When we create a variable with name as PASSWORD the soapUI kind of creates false impression by showing it with "*****" and double clicks makes it visible there.
Are there other best practices handling this type of scenario?
Also is there a feature to may be hide the Raw section (may be I am getting into permissions/authorization here)
Sometimes password management is challing, specially when you need different users with different authorizations and you want to build something for production and say may be share with customer or something outside the company