By default On Demand Services do not provide access to the vcap user password. This article describes a procedure to override the vcap password generated by the bosh director.
This can be useful in cases where an Operator needs to gain direct access to the deployed VM when bosh ssh is not working because instance is in an unresponsive state.
Note: If for some reason you are not able to download the complete manifest because this is the first time the on demand service is being deployed then you can copy a manifest from a good deployment and change the deployment name along with any references to the deployment throughout the manifest.
cf service MY-INSTANCE --guid 11fc56eb-1f89-4e98-a1b2-3c65667412d2
service-instance_11fc56eb-1f89-4e98-a1b2-3c65667412d2
bosh2 -e myenv -d service-instance_11fc56eb-1f89-4e98-a1b2-3c65667412d2 manifest > service-instance_11fc56eb-1f89-4e98-a1b2-3c65667412d2.yml
~$ mkpasswd -s -m sha-512 boshbosh $6$H########H/YR.$uqC2eeHS#############ygadE8Du#################v.LAs2DltR##################
instance_groups: - name: redis-instance instances: 1 env: bosh: password: $6$H######FH/YR.$uqC2ee#########w1smtT.MJtCzM/X#####################rp1v.LAs2DltR########jf50
bosh2 -e myenv -d service-instance_11fc56eb-1f89-4e98-a1b2-3c65667412d2 deploy service-instance_11fc56eb-1f89-4e98-a1b2-3c65667412d2.yml
bosh2 -e myenv -d service-instance_11fc56eb-1f89-4e98-a1b2-3c65667412d2 vms
ssh vcap@