jacksonecac
Enthusiast
Enthusiast

There is a workflow under

Microsoft -> AD -> configurations -> add domain server (I think or similiarly named)

You then provide the domain server's information as well as an account to access the server with. You type in the password in a secure string box so it is not visible to the user or anyone else.

Once that is done it saves the connection string data with the object in the vro database and in doing this it encrypts the password into a hash to store with the domain server connection information. (Using the hashing algorithm you provided in the docs). Any time vro needs to interact with the domain server after that is uses the hashed password that it saved to connect to the domain server.

Also there is a secureString object which does the same thing. You can save any password (in say a local variable in a vro workflow) and it will be hashed and saved in the vro database so any user

could use that particular workflow with the credentials but not know what the password was. (You then could limit the access of that workflow to only qualified users)

https://en.wikipedia.org/wiki/Password-based_cryptography

Vro utilizes the multi-party method. (I believe)