You can customize certificate revocation checking, and you can specify where vCenter Single Sign-On looks for information on revoked certificates.

About this task

You can customize the behavior by using the Platform Services Controller Web interface or by using the sso-config script. The settings that you select depend in part on what the CA supports.

  • If revocation checking is disabled, vCenter Single Sign-On ignores any CRL or OCSP settings.

  • If revocation checking is enabled, the recommended setup depends on the PKI setup.

    OCSP only

    If the issuing CA supports an OCSP responder, enable OCSP and disable using CRL as failover.

    CRL only

    If the issuing CA does not support OSCP, enable CRL checking and disable OSCP checking.

    Both OSCP and CRL

    If the issuing CA supports both an OCSP responder and a CRL, vCenter Single Sign-On checks the OCSP responder first. If the responder returns an unknown status or is not available, vCenter Single Sign-On checks the CRL. For this case, enable both OCSP checking and CRL checking, and enable CRL as failover for OCSP.

  • If revocation checking is enabled, advanced users can specify the following additional settings.

    OSCP URL

    By default, vCenter Single Sign-On checks the location of the OCSP responder that is defined in the certificate being validated. You can explicitly specify a location if the Authority Information Access extension is absent from the certificate or if you want to override it, for example, because it is not available in your environment.

    Use CRL from certificate

    By default, vCenter Single Sign-On checks the location of the CRL that is defined in the certificate being validated. Disable this option when the CRL Distribution Point extension is absent from the certificate or if you want to override the default.

    CRL location

    Use this property if you disable Use CRL from certificate and you want to specify a location (file or HTTP URL) where the CRL is located.

In addition, you can further limit which certificates vCenter Single Sign-On accepts by adding a certificate policy.

Prerequisites

  • Verify that your environment uses Platform Services Controller version 6.0 Update 2 or later, and that you use vCenter Server version 6.0 or later. Upgrade version 5.5 nodes to version 6.0.

  • Verify that an enterprise Public Key Infrastructure (PKI) is set up in your environment, and that certificates meet the following requirements:

    • A User Principal Name (UPN) that corresponds to an Active Directory account in the Subject Alternative Name (SAN) extension.

    • Client Authentication must be specified in the Application Policy or Enhanced Key Usage field of a certificate, or the browser does not show that certificate.

  • Verify that the Platform Services Controller Web interface certificate is trusted by the end user’s workstation; otherwise, the browser does not attempt the authentication.

  • Configure an Active Directory identity source and add it to vCenter Single Sign-On as an identity source.

  • Assign the vCenter Server Administrator role to one or more users in the Active Directory identity source. Those users can then authenticate because they are in the Active Directory group, and they have vCenter Server administrator privileges. The administrator@vsphere.local user cannot perform smart card authentication.

  • If you want to use the Platform Services Controller HA solution in your environment, complete all HA configuration before you set up smart card authentication. See VMware Knowledge base article 2113085 (Windows) or 2113315 (vCenter Server Appliance).

Procedure

  1. From a Web browser, connect to the Platform Services Controller by specifying the following URL:

    https://psc_hostname_or_IP/psc

    In an embedded deployment, the Platform Services Controller host name or IP address is the same as the vCenter Server host name or IP address.

  2. Specify the user name and password for administrator@vsphere.local or another member of the vCenter Single Sign-On Administrators group.

    If you specified a different domain during installation, log in as administrator@mydomain.

  3. Browse to Single Sign-On > Configuration.
  4. Click Certificate Revocation Settings and enable or disable revocation checking.
  5. If certificate policies are in effect in your environment, you can add a policy in the Certificate policies accepted pane.