Creating a Personal Access Token (PAT) for Backup as a Service | Teradata VantageCloud Lake - Use BaaS APIs - Teradata VantageCloud Lake

Lake - Manage and Move Data
Deployment
VantageCloud
Edition
Lake
Product
Teradata VantageCloud Lake
Release Number
Published
February 2025
ft:locale
en-US
ft:lastEdition
2025-05-16
dita:mapPath
atx1683670417382.ditamap
dita:ditavalPath
pny1626732985837.ditaval
dita:id
atx1683670417382

As a VantageCloud Lake customer, you can now access and use the BaaS APIs using the personal access tokens (PAT).

Currently the PAT is enabled only for the DATABASE_USER role.

Limitations

In the current version, the following are some limitations in using the BaaS APIs with the PAT approach:

  • If you are using BYODIP and you update the role mapping, only the customer entries are modified but not the roles in the cloud control plane (CCP).
  • You can access the token even after deleting a BYOIDP user.
  • The account ID shown in the API response is the internal account ID in the format acc-xxx, which is different from what you see on the user interface.

The following are the high-level steps in creating a PAT and accessing BaaS APIs by a customer.

  1. Create a key pair (private and public) on the console.
  2. Create a personal access token (PAT) on the console.
  3. Create a JWT token (you can either use BaaS created script or follow your own steps).
    1. Create a payload for JWT token header and payload.
    2. Create a signature of the header and payload using the private key in step 1.
    3. Creates a JWT token using header, payload, and signature.
  4. Access APIs using the JWT token.

    For PAT creation and security information, contact Teradata account team.