API Token Expiring or is Invalid alerts in VMware Live Cyber Recovery UI
search cancel

API Token Expiring or is Invalid alerts in VMware Live Cyber Recovery UI

book

Article ID: 323644

calendar_today

Updated On:

Products

VMware Live Recovery

Issue/Introduction

Provide the steps to generate a new API Token ID and update it in the VLCR Console for existing deployments, and check to ensure all prerequisites are met when generating an API Token and using in a new deployment of VLCR.


Existing Deployments:

An automated email/Alert is received with the following description, "The API token will expire in 24 days. Create a new API token in VMware Cloud on AWS and add it to VMware Cloud DR. - alert - VMware Cloud DR."

Environment

VMware Live Cyber Recovery 7.26.x and older

Cause


The maximum time to live for an API Token is 60 months. When an API Token is nearing the expiry date, it is required to generate a new token ID and update it within the VLCR product.

Resolution

Note: This article is not applicable for new deployments after August 2024 as OAuth2.0 is used to authorize VLCR to Cloud services and VMC on AWS SDDCs. Refer document Authorize Access for VMware Live Cyber Recovery

Existing Deployments prior to August 2024:

There are two options available:

  1. Regenerate the current API Token used for VLCR.

    Note: Regenerating the current API Token will keep Organization Roles, Service Roles and Time to Live same as before. The step will generate an updated Token ID.

    Or

  2. Create a new API Token and add the same in VLCR console. Follow steps in the document here.

Note: Please make sure the user creating the API Token is an Organization Owner and has all of the correct Service Roles defined in the document.

Additional Information