topic Re: HTTP Synthetic vault issue. in Synthetic Monitoring

HTTP Synthetic vault issue

HeyEngineer — Thu, 18 Dec 2025 11:19:05 GMT

Have an HTTP Synthetic test that has vault credentials. We need to make some changes and we get this message when we try and edit "This monitor uses credentials owned by "xxxxxxxxxxxx", which cannot be used by you. To have full editing privileges, contact the owner or use your own credentials." We don't have access to the token this person used and they are no longer with company. How do we make changes?

Re: HTTP Synthetic vault issue.

p_devulapalli — Wed, 20 Nov 2024 04:34:32 GMT

@HeyEngineer , you can try "Overwrite Credential" and update it with new token if you no longer have access to the earlier token and need to make changes

https://docs.dynatrace.com/docs/shortlink/credential-vault#edit-monitor-with-credential

https://docs.dynatrace.com/docs/shortlink/credential-vault#overwrite-credential

Re: HTTP Synthetic vault issue.

Peter_Youssef — Wed, 20 Nov 2024 05:53:28 GMT

Hello @HeyEngineer

As long as someone with sufficient privileges have created a credential vault and saved it directly into Dynatrace:

Credentials can't be exposed after saving, as it related to the owner and you will observe the related access is to the owner only.
The available scopes as of now "Synthetic" and extension authentication.

As per the raised concern:

Via UI

You can press on Overwrite credential button and then you will be able to update the saved credential parameters.
You have option to keep the used credential parameters in safe repo for future usage.
Another option you can add new credential and specify the previously mentioned parameters as well.

Via Rest API:

Feel free to use any of the available options as highlighted by @p_devulapalli as well.

Hoping it helps

BR,

Peter

Re: HTTP Synthetic vault issue.

Peter_Youssef — Wed, 20 Nov 2024 06:01:48 GMT

Hello @HeyEngineer

A key factor to the resolution checking with the app owners the valid && authorized user credentials 🙂 before saving it into the credential vault to avoid any future authorization errors.

Regards,

Peter