credential vault

Hi ​@Marcin_CF 

Can we know CV version here?

11.32

Hi ​@Marcin_CF ,

Actually, the API supports all types that you see in the console.

The console uses the same API to do its work, so all types are supported.

The API documentation appears to be missing some types.

I requested this be updated.

You can also use the Command Center to create a credential then choose the EQUIVALENT API link on the dialog to show you what the JSON payload would look like.

HI,

i know that generate JSON but smehow it doesnt work do use it to upload . Nice to be see exactly how to do that …..mean example here will be nice to see . I found on forum example  to read credential but seaving new doesnt want to work even using mentioned json 

Hi ​@Marcin_CF ,

I just tried it using a workflow and it saved the credential.  Workflow would be the easiest method because the AuthToken header is handled automatically for you.  But if you are using CURL or some other method, remember that like all these APIs, you must first login and capture the AuthToken and then supply it as a header as mentioned here (bold RED):

curl -L -X POST 'https://CommandCenterHostName/commandcenter/api/V4/Credential' \
-H 'Content-Type: application/json' \
-H 'Accept: application/json' \
-H 'Authtoken: <API_KEY_VALUE>' \
--data-raw '{
"accountType": "WINDOWSACCOUNT",
"vendorType": "ALICLOUD_OSS",
"name": "string",
"userAccount": "string",
"password": "string",
"description": "string"
}'

Here is how I did it using a workflow.  If you are needing to create many as you mention you would need to add additional logic and a for loop to iterate through the different input for each unique one.

The yellow highlight is where the workflow automatically substitutes the login token for you.

Here is the link to the login API that needs to be called first.  Then save the response and supply it in the Authtoken header for all API calls that follow.

https://api.commvault.com/docs/SP38/api/cv/AuthenticationOperations/login/

• token string

  The authentication token that must be inserted into the Authtoken header for all requests