Single Sign-On v1.4

Release Notes

View Release Notes for Another Version

To view the release notes for another product version, select the version from the drop-down list at the top of this page.



Release Date: November 9, 2017

  • PCF updated stemcell to 3445 series. This is a security upgrade to bump Ubuntu stemcells for USN-3420-2: Linux kernel (Xenial HWE) vulnerabilities.


Release Date: October 24, 2017

  • This release addresses an issue with managing service instances when more than 50 Space Developers exist within a space.


Release Date: September 27, 2017

  • This release addresses the upgrade issues for the Single Sign-On Service tile when legal footer links are configured.
  • This release addresses a Java Buildpack issue that causes required memory to increase to 1GB.


Release Date: August 30, 2017

Additional information can be found at


Release Date: June 21, 2017

  • PCF updated stemcell to 3363 series. This is a security upgrade to bump Ubuntu stemcells for USN-3334-1: Linux kernel (Xenial HWE) vulnerabilities.


Release Date: June 15, 2017

What’s New

  • Application bootstrapping is available for app developers to automates and quickly onboard client and resource configurations to Single Sign-On. See the Set Up PCF Apps to Use SSO topic for more information.

  • Admin User Management interface enables plan administrators to browse and manage users across their identity providers through a simple user interface as opposed to through the UIs to help improve productivity. See the Manage Users topic for more information.

  • OpenID Connect and LDAP identity provider interfaces are now available. Plan administrators can now improve their productivity by utilizing a simple user interface to configure and maintain their identity providers. See the Configure Identity Providers topic for more information.

  • You can allow custom attributes to be made available through the /userinfo endpoint for your external identity providers. This can streamline user attributes for your applications. Your application must have the user_attributes token once custom attributes mappings and Persist Custom Attributes are configured for your identity provider.

  • You can configure required user groups through bootstrapping. Require user groups are groups that users must have in order to authenticate to your application and obtain an access token.

Create a pull request or raise an issue on the source for this page in GitHub