Client ID created with access type 'Service client token' in VIDM shows up as not activated

Products

• VCF Automation

Issue/Introduction

Client ID shows as not activated in the UI (catalog>settings>remote app access)

Environment

VIDM 3.3.7

Cause

Client ID showing not activated is expected for third party app integration with VIDM using the service client token.

Resolution

An admin-scoped client functions as a Service Client Token (using the client_credentials grant for backend and machine automation, rather than being tied to a signed-in user). Its "Not Activated" status indicates that its automatically generated ActivationToken row is still present in the database and has not yet been redeemed through the one-time activation API endpoint.

However if you still want to activate it you can follow the below steps 

Activate the Service Client Token  
curl -sk -X POST https://<VIDM-Host>/SAAS/API/1.0/REST/oauth2/activate \  -H 'Content-Type: application/json' \
  -d ‘”<activation-token>”’

Sample result :{ "client_id":"vra-xx”,”client_secret”:”xxxxxxx”}

 

Additional Information

This is a private API hence it will not be available in public API docs.