spring.cloud.vault:
+ authentication: PCF
+ pcf:
+ role: my-dev-role
+diff --git a/reference/html/index.html b/reference/html/index.html index 447cc678..62fc30cf 100644 --- a/reference/html/index.html +++ b/reference/html/index.html @@ -118,6 +118,7 @@ $(addBlockSwitches);
The pcf +auth backend provides a secure introduction mechanism for applications running within Pivotal’s CloudFoundry instances allowing automated retrieval of a Vault token. +Unlike most Vault authentication backends, this backend does not require first-deploying, or provisioning security-sensitive credentials (tokens, username/password, client certificates, etc.) as identity provisioning is handled by PCF itself. +Instead, it treats PCF as a Trusted Third Party and uses the managed instance identity.
+spring.cloud.vault:
+ authentication: PCF
+ pcf:
+ role: my-dev-role
+spring.cloud.vault:
+ authentication: PCF
+ pcf:
+ role: my-dev-role
+ pcf-path: path
+ instance-certificate: /etc/cf-instance-credentials/instance.crt
+ instance-key: /etc/cf-instance-credentials/instance.key
+role sets the name of the role against which the login is being attempted.
pcf-path sets the path of the PCF mount to use.
instance-certificate sets the path to the PCF instance identity certificate.
+Defaults to ${CF_INSTANCE_CERT} env variable.
instance-key sets the path to the PCF instance identity key.
+Defaults to ${CF_INSTANCE_KEY} env variable.
| + + | ++PCF authentication requires BouncyCastle (bcpkix-jdk15on) to be on the classpath for RSA PSS signing. + | +
spring-cloud-vault-config-consul
spring.cloud.vault.consul.token-property
spring.cloud.vault.rabbitmq.username-property and
dependency.
spring.cloud.vault.mysql.role.backend=database.
The pcf +auth backend provides a secure introduction mechanism for applications running within Pivotal’s CloudFoundry instances allowing automated retrieval of a Vault token. +Unlike most Vault authentication backends, this backend does not require first-deploying, or provisioning security-sensitive credentials (tokens, username/password, client certificates, etc.) as identity provisioning is handled by PCF itself. +Instead, it treats PCF as a Trusted Third Party and uses the managed instance identity.
+spring.cloud.vault:
+ authentication: PCF
+ pcf:
+ role: my-dev-role
+spring.cloud.vault:
+ authentication: PCF
+ pcf:
+ role: my-dev-role
+ pcf-path: path
+ instance-certificate: /etc/cf-instance-credentials/instance.crt
+ instance-key: /etc/cf-instance-credentials/instance.key
+role sets the name of the role against which the login is being attempted.
pcf-path sets the path of the PCF mount to use.
instance-certificate sets the path to the PCF instance identity certificate.
+Defaults to ${CF_INSTANCE_CERT} env variable.
instance-key sets the path to the PCF instance identity key.
+Defaults to ${CF_INSTANCE_KEY} env variable.
| + + | ++PCF authentication requires BouncyCastle (bcpkix-jdk15on) to be on the classpath for RSA PSS signing. + | +
spring-cloud-vault-config-consul
spring.cloud.vault.consul.token-property
spring.cloud.vault.rabbitmq.username-property and
dependency.
spring.cloud.vault.mysql.role.backend=database.