Management Pack Builder

 View Only

  • 1.  vROps monitoring vROps authentication

    Posted Sep 03, 2025 10:30 AM

    Use case for a mgmt pack:  Collect License data (key, total, edition, usage, expiration) from all other vROps 8.18 clusters for reporting purposes using suite-api/api/deployment/licenses.  With basic auth on the suite-api disabled, how to authenticate?  Using custom authentication with the following headers (Authorization = vRealizeOpsToken ${authentication.session.token}) , after installing the mgmt pack on the same cluster used as source, it collects fine.  Any other cluster I try to add, gets 401 error The provided username/password or token is not valid. Please try again.  What am I missing here??



    -------------------------------------------


  • 2.  RE: vROps monitoring vROps authentication
    Best Answer

    Broadcom Employee
    Posted Sep 04, 2025 08:41 AM

    Hi @FredGSanford -- as long as you don't hardcode any credentials or configuration fields, the MPs generated by MP Builder should be generic and reusable across multiple environments. Here are some screenshots from a working Suite API design (taken from VCF Ops 9.x, but should be similar to MPB 2.0).

    -------------------------------------------



  • 3.  RE: vROps monitoring vROps authentication

    Posted Sep 04, 2025 09:08 AM

    That was it, thanks Mark!  Found this post yesterday and resolved it by using the variables in the body.  

    https://community.broadcom.com/vmware-cloud-foundation/discussion/source-with-session-authentication-the-request-body-is-not-parsed-correctly

    -------------------------------------------

    Original Message