How to use access token generated in the web portal in API calls?

In the Command Center you’re creating a bearer token, so the usage is

Bearer [and here the long string received during bearer token creation]

On the other hand, if you created a “regular” QSDK token ie. in /webconsole/sandbox, then the usage is

QSDK [and here the long string]
 

In total three headers are required:

        'Authorization' = '[here put QSDK or Bearer token]'
        'Accept' = 'application/xml'
        'Content-type' = 'application/json or xml'
 

Hope that helps.

Thank you so much for your quick response. I tried to reperform what you said but unfortunately it didn’t work. Are you aware of what I did wrong?

This seems to be metallic related… ​

Anyone can help with this? Thanks.

Took a bit:)

• Run /login
• Take the authtoken QSDK string from the output
• Use the header Authorization: Bearer QSDK string

So an example to list hypervisors after getting authtoken as “QSDK 3ad83249f8395acaa54605aef429bf1a38a0d68c8e3f34e7fa136a15a8c0832d79f73109fd10629a4c29c” from /Login you’d run:
GET against https://api.metallic.io/v4/hypervisor with the below headers
"Accept: application/json"
"Content-type: application/json"
“Authorization: Bearer QSDK 3ad83249f8395acaa54605aef429bf1a38a0d68c8e3f34e7fa136a15a8c0832d79f73109fd10629a4c29c"

Thank you for the reply. The “/Login” case did work if i provide username and password. However, i have mulit-factor authentication enabled and i couldn’t just use username and password to get the access token from “https://api.metallic.io/Login”.

This is the reason why i want to generate the access token from the portal for long-term usage.

Interestingly, I have tested the same setup to get access token from my on-premise Commvault instance and it works fine. Just the cloud version didn’t work.

The behaviour and the must of using /Login is explained :

https://docs.metallic.io/metallic/rest_api.html?_gl=1*lp168n*_gcl_au*MTUxMDY3NzE5NC4xNzM2NTgzODA5
 

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

Got it. If all my cloud accounts are all MFA enabled, how can i authenticate to metallic APIs using “/login”?

It is quite simple:

You use your email as a username and base64 encoded password+pin from whatever TFA solution you’re using.

Example:

user: jacek@test.lab
regular password: #test123@

the PIN received from the 2FA app: 125486

the pass to provide to base64 encoder: #test123@125486
the string returned by the base64 encoder: I3Rlc3QxMjNAMTI1NDg2

the username to provide to REST /Login: jacek@test.lab
the password to provide to REST /Login: I3Rlc3QxMjNAMTI1NDg2