certificate relies on legacy Common Name field, use SANs or temporarily enable Common Name after go upgrade. about app-autoscaler-release

[garethjevans]

Another suggestion could be to generate the certificates for postgres with the alternative_names correctly configured.

[mmavrudiev]

Not working, if I put only alternative_names to the CAs, getting:

                 L Error: Config Server failed to generate value for '/overbosh/app-autoscaler/scalingengine_ca' with type 'certificate'. HTTP Code '400', Error: 'At least one subject value, such as common name or organization, must be defined to generate the certificate. Please update and retry your request.'

If I put organization + alternative_names I am getting:

2021/07/23 07:59:37 failed-to-connection-to-database, dburl:postgres://postgres:[e-mail]:5432/autoscaler?sslmode=verify-full&sslrootcert=/var/vcap/jobs/scalingengine/config/certs/scalingengine_db/ca.crt, err:x509: certificate relies on legacy Common Name field, use SANs or temporarily enable Common Name matching with GODEBUG=x509ignoreCN=0

If I put common_name + alternative_names getting the above error.

[garethjevans]

@mmavrudiev did you have any success setting the GODEBUG variable? e.g. #288?

[mmavrudiev]

@garethjevans have not tried in utils.sh but was trying to set the env var on every pre-start script, let me try that one as well.

[mmavrudiev]

@garethjevans I have tried the same mentioned in #288 but getting the same cert error - err:x509: certificate relies on legacy Common Name field, use SANs or temporarily enable Common Name matching with GODEBUG=x509ignoreCN=0, then executing ./scripts/update, then have created the bosh release, then uploading the release and using it to create the bosh deployment.

[garethjevans]

Fixed by #325