Skip to main content
Solved

Does the reports API accept bearer tokens?


christopherlecky
Byte
Forum|alt.badge.img+17

The documentation appears to be contradictory.

https://documentation.commvault.com/2024e/expert/rest_api_get_data_set.html

GET /CustomReportsEngine/rest/reportsplusengine/datasets/<datasetID>/data 
Host: <host name>
Accept: application/xml
Authtoken: <authentication token>

When I attempt to use a bearer token, I get 401 not authenticated.

 

Best answer by RMcG

I hit this recently and there’s a hotfix in the works (possibly already released) that should resolve it. Should be getting backported to FR32, FR34 and FR36.

I was informed that for the custom reports engine APIs you should be able to workaround the issue by adding QSDK and a space before the token eg [QSDK<space>Access token string] instead of the bearer token prefix. Haven’t tried that myself though… just went back to using the classic QSDK Token in the AuthToken header approach for the time being.

View original
Did this answer your question?

2 replies

Forum|alt.badge.img+6
  • Vaulter
  • 30 replies
  • Answer
  • March 10, 2025

I hit this recently and there’s a hotfix in the works (possibly already released) that should resolve it. Should be getting backported to FR32, FR34 and FR36.

I was informed that for the custom reports engine APIs you should be able to workaround the issue by adding QSDK and a space before the token eg [QSDK<space>Access token string] instead of the bearer token prefix. Haven’t tried that myself though… just went back to using the classic QSDK Token in the AuthToken header approach for the time being.


christopherlecky
Byte
Forum|alt.badge.img+17
RMcG wrote:

I hit this recently and there’s a hotfix in the works (possibly already released) that should resolve it. Should be getting backported to FR32, FR34 and FR36.

I was informed that for the custom reports engine APIs you should be able to workaround the issue by adding QSDK and a space before the token eg [QSDK<space>Access token string] instead of the bearer token prefix. Haven’t tried that myself though… just went back to using the classic QSDK Token in the AuthToken header approach for the time being.

 

Awesome, I will try the QSDK thing.

 

I am using the bearer token to update excel spreadsheets and had to write a login script just to get the data. 

Super annoying. 

Thanks.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings