LATEST VERSION: 1.5 - CHANGELOG
Spring Cloud Services v1.0

Prerequisites to Installing Spring Cloud Services for Pivotal Cloud Foundry®

Page last updated:

Please ensure that your Pivotal Cloud Foundry® (PCF) installation meets the below requirements before installing Spring Cloud Services.

Platform and Product Requirements

Spring Cloud Services is compatible with the Java buildpack at the version shipped with Pivotal Cloud Foundry® Elastic Runtime or later. At minimum, Spring Cloud Services requires version 2.5 or later of the Java buildpack; it is recommended that you use the latest buildpack version possible. You can use the Cloud Foundry Command Line Interface tool (cf CLI) to see the version of the Java buildpack that is currently installed.

$ cf buildpacks
Getting buildpacks...

buildpack                position   enabled   locked   filename
java_buildpack_offline   1          true      false    java-buildpack-offline-v3.0.zip
ruby_buildpack           2          true      false    ruby_buildpack-cached-v1.3.1.zip
nodejs_buildpack         3          true      false    nodejs_buildpack-cached-v1.2.1.zip
go_buildpack             4          true      false    go_buildpack-cached-v1.2.0.zip

If the default Java buildpack is older than version 2.5, you can download a newer version from Pivotal Network and update Pivotal Cloud Foundry® by following the instructions in the Adding Buildpacks to Cloud Foundry topic. If you do not delete or disable the older Java buildpack, make sure that the newer Java buildpack is in a lower position so that it will be the default.

Spring Cloud Services also requires the following Pivotal Cloud Foundry® products:

If they are not already installed, you can follow the steps listed in the Installation subtopic to install them along with Spring Cloud Services.

Security Requirements

You will need to update your Elastic Runtime SSL certificate as described in the Pivotal Cloud Foundry® documentation. Generate one single certificate that includes all of the domains listed below, replacing SYSTEM_DOMAIN.TLD with your system domain and APPLICATION_DOMAIN.TLD with your application domain:

  • *.SYSTEM_DOMAIN.TLD
  • *.APPLICATION_DOMAIN.TLD
  • *.login.SYSTEM_DOMAIN.TLD
  • *.uaa.SYSTEM_DOMAIN.TLD

If any of these domains are not attributed to your Elastic Runtime SSL certificate, the installation of Spring Cloud Services will fail, and the installation logs will contain an error message that lists the missing domain entries:

Missing certs: *.uaa.example.com - exiting install. Please refer to the Security
Requirements section of the Spring Cloud Services prerequisites documentation.

Self-Signed Certificates and Internal CAs

If your Pivotal Cloud Foundry® installation is using its own self-signed SSL certificate, you must enable the “Trust Self-Signed Certificates” or “Ignore SSL certificate verification” option in the Networking section of the Pivotal Elastic Runtime tile Settings tab. See Step 4 of the Configuring Elastic Runtime for vSphere and vCloud topic in the Pivotal Cloud Foundry® documentation.

If you are using an SSL certificate signed by an internal root Certificate Authority (CA), you must use a custom Java buildpack whose keystore contains the internal root CA. Follow the below steps to create and add the custom buildpack.

  1. Create a fork of the Cloud Foundry Java buildpack.
  2. Add your cacerts file to resources/open_jdk_jre/lib/security/cacerts.
  3. Following the instructions in the Adding Buildpacks to Cloud Foundry topic, add your custom buildpack to Pivotal Cloud Foundry®.
  4. Using the cf CLI as discussed in the Platform and Product Requirements section above, verify that the custom buildpack is now the default Java buildpack.
Create a pull request or raise an issue on the source for this page in GitHub