Skip to main content
Question

Incorrect credential api response

  • December 19, 2024
  • 2 replies
  • 32 views

Forum|alt.badge.img

It seems that the api to GET the credential returns endpoint with a different key as compare to what is expected by PUT api for updating the credential . 

API : /commandcenter/api/v5/credential/:credentialid

Even from the document the key name is different from what is returned.

 

As you can see from actual output , we get extra “Endpoint” in the key name.

 

This results the automation of GET and PUT request , to remove the endpoint completely . I agree that we can modify it in the automation before hitting PUT , but I still feel this is a BUG. Any one faces / observed this issue ?

 

2 replies

Jon Vengust
Vaulter
Forum|alt.badge.img+6
  • Vaulter
  • 33 replies
  • December 20, 2024

Hi Raj, thanks for raising this matter.

 

I’ll follow-up internally on this request to seek some clarity for you hopefully by EOW.

 

In the meantime, whilst the workaround is sufficient, you are correct as it shouldn’t be expected based on our current documentation.


Jon Vengust
Vaulter
Forum|alt.badge.img+6
  • Vaulter
  • 33 replies
  • January 17, 2025

Hi Raj, apologies for the delay over the holiday period.

 

I’ve followed up on this matter internally and can confirm our development team are working to resolve this matter. Our documentation will be updated to reflect the correct format and will include the endpoint suffix going forward. We are currently pending internal review before going live with this change hopefully within the month.

 

We appreciate you bringing this to light. Thanks again!


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