This short video demonstrates how to run Pivotal CRM and Microsoft Outlook on Mac OS X utilizing virtualization.
Page last updated:
This topic describes how developers can use the Cloud Foundry Command Line Interface (cf CLI) to communicate securely with a Pivotal Platform deployment with a self-signed certificate.
You can use the cf CLI to communicate securely with a Pivotal Platform deployment without specifying --skip-ssl-validation
under these circumstances:
The deployment uses a self-signed certificate.
The deployment uses a certificate that is signed by a self-signed certificate authority (CA), or a certificate signed by a certificate that is signed by a self-signed CA.
Before following the procedure below, the developer must obtain either the self-signed certificate or the intermediate and CA certificate(s) used to sign the deployment’s certificate. The developer can obtain these certificates from the Pivotal Platform operator.
The certificates you must insert into your local truststore vary depending on the configuration of your deployment.
If the deployment uses a self-signed certificate, the you must insert the self-signed certificate into your local truststore.
If the deployment uses a certificate that is signed by a self-signed CA, or a certificate signed by a certificate that is signed by a self-signed CA, you must insert the self-signed certificate and any intermediate certificates into your local truststore.
To place the certificate file server.crt
into your local truststore for Mac OS X:
Run:
To place the certificate file server.crt
into your truststore for Linux:
Run one of these commands, depending on your Linux distrubution:
For Debian, Ubuntu, or Gentoo, run:
For Fedora or RHEL, run:
The examples above set the certificate permanently on your machine across all users and require sudo
permissions. To set the certificate only in your current terminal or script, run one of these commands:
export SSL_CERT_FILE=PATH-TO-SERVER.crt
Where PATH-TO-SERVER.crt
is the filepath of the server.crt
certificate file.
export SSL_CERT_DIR=PATH-TO-SERVER-DIRECTORY
Where PATH-TO-SERVER-DIRECTORY
is the directory of the server.crt
certificate file.
To place the certificate file server.crt
into your local truststore for Windows:
Right-click on the certificate file.
Click Install Certificate.
Choose to install the certificate as the Current User or Local Machine.
From the certification store list, select Trusted Root Certification Authorities.
Page last updated:
This topic describes how to deploy and use the Spring Cloud® Services (SCS) suite within PCF Dev.
When configured to use SCS, PCF Dev provides the following services:
The sections below describe how to launch SCS and use the Config Server. The Service Registry and Circuit Breaker Dashboard work by default when PCF Dev is launched with SCS enabled.
To launch PCF Dev using SCS, run cf dev start
using the -s scs
flag:
Note: Due to the increased demands of SCS, PCF Dev allocates more memory than usual.
Alternatively, you can deploy SCS after start by running the following command:
To undeploy SCS, stop PCF Dev:
To create a service instance of the Config Server using the cook sample app, perform the following:
Clone the cook sample app to your workspace.
In a terminal window, navigate to the root repository of the cook sample app.
To compile the cook sample app, run one of the following commands:
./gradlew build
gradlew.bat build
For example, the output on Mac OS X appears as follows:
Run cf login
to log in to PCF Dev and target your local domain using user/pass as the credentials. To avoid SSL validation errors, use the --skip-ssl-validation
flag. See SSL Validation Errors.
Run cf create service
to create a service instance of the config server. Use the -c
flag to specify a JSON object containing configuration parameters for the service as show in the following example:
Run cf service config-server
to confirm that the service was created:
When finished, the status of the service instance displays create succeeded
.
Push the compiled JAR file:
Navigate to http://cookie.local.pcfdev.io/restaurant to view the cook app.
Note: PCF Dev uses an unverified certificate. When a PCF Dev SCS service makes use of an unverified certificate, the pushed apps must have the environment variable CF_TARGET
set to the api URL of the PCF Dev instance: https://api.local.pcfdev.io
. PCF Dev does this by default for all pushed apps.
To manage an SCS instance within PCF Dev, navigate to Apps Manager and log in using the admin credentials, admin/admin
. Instances of the SCS services are displayed in the instances space of the p-spring-cloud-services org. See the Use Apps Manager topic for more information.