Management Pack Builder

 View Only
  • 1.  401 Unauthorized

    Posted Jun 06, 2024 06:42 PM

    I'm having some trouble with almost all GET requests via the Veeam API.

    I was able to set up the source successfully, and store the access token for the session, I using the Veeam API call "api/v1/serverinfo" for the connection test successfully.

    However, when I try to set up any other requests apart from to "api/v1/serverinfo" it throws back a "401 unauthorized" response.

    I know I have everything configured correctly and I am able to successfully get a response from only "api/v1/serverinfo" but literally every other GET request fails via MP Builder and is successful via Postman.

    I am running MP Builder 1.1.3 (acquired via our TAM to fix a separate issue).

    Could this be an MP Builder bug?



  • 2.  RE: 401 Unauthorized

    Broadcom Employee
    Posted Jun 07, 2024 09:53 AM

    Hi,

    "401 unauthorized" indicates a problem with the token or, more precisely, how the token is retrieved, stored in a variable, and used in subsequent requests. Can you post a few screenshots showing the authentication configuration? Both for the token acquisition call and one of the subsequent calls.

    Thomas




  • 3.  RE: 401 Unauthorized

    Posted Jun 10, 2024 09:28 AM
    Edited by Ashley Vercammen Jun 10, 2024 09:32 AM

    Hi Thomas,

    After some further testing when getting screenshots I figured out the issue, I added "bearer" to the global variable for the Authorization header and it seems to be working now.

    Very strange as the /api/v1/serverinfo call works without the "bearer" word inserted and just the access key variable, but looks like other requests require "bearer" to be added...



  • 4.  RE: 401 Unauthorized

    Broadcom Employee
    Posted 30 days ago

    Hi,

    Glad that you could resolve it.

    I don't have a Veeam environment here but according to this documentation (https://helpcenter.veeam.com/docs/backup/vbr_rest/requesting_authorization.html?ver=120) the Authorization has to include the Bearer statement, which is a very common authorization.

    Authorization:Bearer eyJhbGciOiJSUzUxM....

    Best regards,

    Thomas