vCenter Single Sign On SDK 2.0 Release Notes

Released 22 SEPT 2013

Updated: 15 MAR 2016

 

Any version numbers referenced are placeholders and do not represent any commitment by VMware to have any specific features in the beta software included in any specific versions.

vCenter Single Sign On SDK 2.0 is included in the vSphere Management SDK for vSphere 5.5 and 6.0.

This document contains the following information:

Overview

vSphere 5.5 and 6.0 include the vCenter Single Sign-On Server that provides a Security Token Service for authentication services in the vSphere environment. The vCenter Single Sign-On SDK provides an API that your client application can use to obtain SAML (Security Assertion Markup Language) tokens for logging in to a vCenter Server.

For information about how to use the vCenter Single Sign On API, see the vCenter Single Sign On Programming Guide.

For vSphere 5.5 and 6.0, C# examples have been added to the VMware Single Sign On SDK. Information about the C# examples has been added to the vCenter Single Sign On Programming Guide.

The vCenter Single Sign-On SDK now supports Java 8.

Distribution Kit

The vCenter Single Sign On SDK is distributed as part of the vSphere Management SDK. The vSphere Management SDK is a collection of vSphere SDKs. When you extract the contents of the distribution kit, the vCenter Single Sign On SDK is contained in the SDK/ssoclient sub-directory:

VMware-vSphere-SDK-6.0.0-2505176
    SDK
        eam
        sms-sdk
        spbm
        ssoclient
        vsphere-ws

Documentation

For information about the vCenter Single Sign On API, see the vCenter Single Sign On documentation.

Known Issues

  • Description for VASA system events and alarms is "Unknown Event ID:".

    The vSphere Client displays VASA system events for the root folder of the inventory or for the datastore associated with the storage device. The vCenter Server uses the string "Unknown Event ID:" for the event description instead of the message specified in the VASA Provider message catalog.

    • Resolved Issues

  • Acquiring a Holder of Key (HoK) SAML token using a key/certificate pair generated during runtime, fails with JDK 1.8.

    The samples in the SSO SDK use Java X.509 certificate libraries to create a certificate as a convenience to the user. A change in JDK 1.8 caused the samples in this SDK to fail with a java.security.cert.CertificateException.

    This problem has been corrected.