Installing Pivotal Single Sign-On
This topic explains how to install Pivotal Single Sign‑On.
To install Single Sign‑On, you must have:
Note: If you are upgrading to this version of Single Sign‑On, you must update the definitions of any BOSH Add-Ons you are using to include the Xenial stemcell. See Update Add-ons to Run with Xenial Stemcell below.
From Pivotal Network, select a Single Sign‑On tile version and download the product release file.
From the Ops Manager Installation Dashboard, select the Import a Product button to upload the product file.
Click the + icon next to the uploaded product to add this product to your staging area.
Click on the Single Sign‑On tile to enter any configurations.
Note: The Single Sign‑On Identity Service Broker is deployed as an app from a BOSH errand, and has no associated BOSH VMs that require selecting a corresponding network. If you are forced to select a network during installation, select the Deployment network, also known as the Pivotal Application Service network.
In the Ops Manager Dashboard, do the following to complete the installation:
- If you are using Ops Manager v2.3 or later, click Review Pending Changes.
For more information about this Ops Manager page, see
Reviewing Pending Product Changes.
- Click Apply Changes.
- If you are using Ops Manager v2.3 or later, click Review Pending Changes. For more information about this Ops Manager page, see Reviewing Pending Product Changes.
If required, do the following to update the stemcell for Single Sign‑On:
- Download the stemcell from Pivotal Network.
- In the Ops Manager, click Stemcell Library.
Click Import Stemcell, and then select the stemcell you downloaded from Pivotal Network.
You must update the SSL certificate for the domains listed below for each plan you create. Depending on your infrastructure and load balancer, you must also update your load balancer configuration for the following domains:
Single Sign‑On requires the following network connections:
- TCP connection to load balancer(s) on port 443
- TCP and UDP connection to Domain Name Servers on port 53
- (Optional) TCP connection to your external identity provider on port 80 or 443
To enable access to Single Sign‑On, you must ensure your ASG allows access to the load balancer(s) and domain name servers that provide access to Cloud Controller and UAA. Optionally, you can configure access to your external identity provider to receive SAML metadata. For how to set up ASGs, see Application Security Groups.
Single Sign‑On v1.7.1 and later requires a Xenial stemcell. If you are using any of the following BOSH Add-ons with your deployment, you must update the add-on definition to include the Xenial stemcell before you deploy Single Sign‑On v1.7.1:
- Pivotal File Integrity Monitoring. For update instructions, see Updating Pivotal File Integrity Monitoring to Run with Xenial Stemcells.
- Pivotal Anti-Virus. For update instructions, see Updating Pivotal Anti-Virus to Run with Xenial Stemcells.
- Pivotal IPsec. For update instructions, see Updating Pivotal IPsec to Run with Xenial Stemcells.