You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a Service Binding exists that provides private-key for type postgresql then spring cloud bindings should add sslkey to the JDBC url that points to the file location that contains the contents for the private-key.
When a Service Binding exists that provides certificates for type postgresql then spring cloud bindings should add sslcert to the JDBC url that points to the file location that contains the contents for the certificates.
I see there is already a way to add some additional DB options:
I'm wondering if this can already be leveraged to add in missing parameters for sslcert and sslkey which are necessary for TLS Authentication to Postgres databases.
So this issue might just be documenting how to add those parameters, and how to populate them with a TLS certificate added through certificates and private-key are populated as well-known Secret Entries , but at first glance I don't think this functionality works properly.
The text was updated successfully, but these errors were encountered:
private-key
for typepostgresql
then spring cloud bindings should addsslkey
to the JDBC url that points to the file location that contains the contents for theprivate-key
.certificates
for typepostgresql
then spring cloud bindings should addsslcert
to the JDBC url that points to the file location that contains the contents for thecertificates
.I see there is already a way to add some additional DB options:
spring-cloud-bindings/spring-cloud-bindings/src/main/java/org/springframework/cloud/bindings/boot/PostgreSqlBindingsPropertiesProcessor.java
Line 111 in 7f20fb2
I'm wondering if this can already be leveraged to add in missing parameters for
sslcert
andsslkey
which are necessary for TLS Authentication to Postgres databases.So this issue might just be documenting how to add those parameters, and how to populate them with a TLS certificate added through
certificates
andprivate-key
are populated as well-known Secret Entries , but at first glance I don't think this functionality works properly.The text was updated successfully, but these errors were encountered: