Question on Bosh Director using CredHub to generate passwords

Michael Stancampiano

Wanted to verify the steps that Bosh Director and CredHub perform to generate a password during a deployment. Here are the assumed steps:
1) Director does a CredHub REST API GET call to obtain the value for an identifier in a manifest file.
2) CredHub returns a status code of not found (404).
3) Generate password properties exist in the manifest file for the identifier. So Director makes a CredHub REST API POST call to generate the password value passing in the specified password properties from the manifest file.
4) CredHub returns a generated password value.

Please confirm these are the processing steps invoked by the Director. Also confirm that if no generate password properties are present in the manifest file for the identifier then no POST call is made to CredHub.


Join { to automatically receive all group messages.