LATEST VERSION: v1.3 - RELEASE NOTES

Pivotal Container Service v1.3

• v1.2
• v1.1
• v1.0

PDF

Configuring PKS API Access

Page last updated:

This topic describes how to configure access to the Pivotal Container Service (PKS) API. See PKS API Authentication for more information about how the PKS API and UAA interact with your PKS deployment.

Configure Access to the PKS API

1. Locate your Ops Manager root CA certificate.

   • If Ops Manager generated your certificate, refer to the Retrieve the Ops Manager Root Certificate section of Managing Certificates.
   • If you provided your own certificate, copy and paste the certificate you entered in the PKS API pane into a file.

2. Target your UAA server by running the following command:

   uaac target https://PKS-API:8443 --ca-cert ROOT-CA-FILENAME

   Replace the following values:
   • PKS-API: enter the fully qualified domain name (FQDN) you use to access the PKS API. You configured this URL in the PKS API section of Installing PKS for your IaaS. For example, see Installing PKS on vSphere.
   • ROOT-CA-FILENAME: enter the path for the certificate file you downloaded in a previous step. For example:

     $ uaac target api.pks.example.com:8443 --ca-cert my-cert.cert
     

     Including https:// in the PKS API URL is optional.

3. Run uaac token client get admin -s UAA-ADMIN-SECRET to request a token from the UAA server. Replace UAA-ADMIN-SECRET with your UAA admin secret. Refer to Ops Manager > Pivotal Container Service > Credentials > Pks Uaa Management Admin Client to retrieve this value.

4. Grant cluster access to new or existing users with UAA. For more information on granting cluster access to users or creating users, see the Grant PKS Access to a User section of Managing Users in PKS with UAA.

Log in to the PKS CLI as a User

For information about logging in to the PKS CLI as a user, see the Log in to PKS CLI section of Installing the PKS CLI.

Log in to PKS as an Automated Client

On the command line, run the following command to log in to the PKS CLI as an automated client for a script or service:

pks login -a PKS-API --client-name CLIENT-NAME --client-secret CLIENT-SECRET --ca-cert CERTIFICATE-PATH

Where:

• PKS-API is the domain name for the PKS API that you entered in Ops Manager > Pivotal Container Service > PKS API > API Hostname (FQDN). For example, api.pks.example.com.

• CLIENT-NAME is your OAuth client ID.

• CLIENT-SECRET is your OAuth client secret.

• CERTIFICATE-PATH is the path to your root CA certificate. Provide the certificate to validate the PKS API certificate with SSL.
  
  

For example:

$ pks login -a api.pks.example.com \
--client-name automated-client \
--client-secret randomly-generated-secret \
--ca-cert /var/tempest/workspaces/default/root_ca_certificate