Hello again Asha, Yes, the predefined secret names in an RSA container should match up with secret refs for those actual things. “private_key” should point to the private key of the RSA pair, “public_key” should point to the matching public key.
private_key_passphrase is optional, and it is only used for passphrase-protected keys. It should point to a secret that has the plain text passphrase used to unlock the private key. -Doug -------------------- Douglas Mendizábal IRC: redrobot PGP Key: 245C 7B6F 70E9 D8F3 F5D5 0CC9 AD14 1F30 2D58 923C > On Mar 16, 2015, at 5:29 PM, Asha Seshagiri <asha.seshag...@gmail.com> wrote: > > Hi All, > > Lastly , I would like to know whether the predefined secret names > "private_key”, “public_key”, and “private_key_passphrase” in RSA containers > has any logical relation with the secret reference. > > For ex : If the name of the secret is private_key , should the secret_ref be > necessarily a private_key .Does the same thing holds good with the public > key as well. > > What is private_key_passpharse and what is the difference between private_key > and private_key_passpharse ? > > It would be great if anyone could help me on this . > Thanks in advance ! > -- > Thanks and Regards, > Asha Seshagiri > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
signature.asc
Description: Message signed with OpenPGP using GPGMail
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
