# Issues with adding Auth0 Vault Connection

**URL:** <https://community.auth0.com/t/issues-with-adding-auth0-vault-connection/137355>\
**Category:** Get Help\
**Tags:** login-experience, new-universal-login-experience\
**Created:** [June 25, 2024, 12:34pm UTC](https://community.auth0.com/t/issues-with-adding-auth0-vault-connection/137355 "2024-06-25T12:34:22Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![niklas.michel](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@niklas.michel](https://community.auth0.com/u/niklas.michel)\
**Post date:** [June 25, 2024, 12:34pm UTC](https://community.auth0.com/t/issues-with-adding-auth0-vault-connection/137355/1 "2024-06-25T12:34:22Z")

</div>

Hello, I have built a customised Onboarding form based on the template provided by Auth0.

Now I am struggling with adding a vault connection, I have created a M2M Application which is authorized to use my custom API with all the needed scopes.

The error I am getting indicates that I am using the wrong credentials.

I have copied the domain, client id and client secret directly from the settings tab.  
I have read about other users accidentally using the wrong application type, but I am more than sure I use a M2M App.

I’ve been trying around for pretty long already, I can’t seem to find whats wrong.

I appreciate any help, thanks!

 ![Screenshot 2024-06-25 at 14.29.57](https://global.discourse-cdn.com/auth0/original/3X/c/f/cfd83e7d0539efbd542cc71110f3524dae52ab8e.png)

---

<div class="post-metadata">

**Author:** ![dawid.matuszczyk](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/dawid.matuszczyk/32/74550_2.png) [@dawid.matuszczyk](https://community.auth0.com/u/dawid.matuszczyk)\
**Post date:** [June 25, 2024, 1:58pm UTC](https://community.auth0.com/t/issues-with-adding-auth0-vault-connection/137355/2 "2024-06-25T13:58:30Z")

</div>

Hi @niklas.michel

Welcome to the Auth0 Community!

Thank you for posting your question. I’ve checked your tenant settings and logs, and I think that this issue can be caused by your M2M not being privileged to the Management API. It’s necessary to authorize the Auth0 Managment API application.

 ![Screenshot 2024-06-25 at 15.56.05](https://global.discourse-cdn.com/auth0/original/3X/4/2/4289d01a4ca849edb55000b40ee8c863c258aa5c.jpeg)

If you want to use your owned API from Vault view, you can select HTTP, but it’s only support access token for now.

 ![Screenshot 2024-06-25 at 15.57.17](https://global.discourse-cdn.com/auth0/original/3X/1/2/129aeee5a3881ca1c19a4ee7619d2692c9eda1af.png)

I hope this will help you!

Dawid

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [July 9, 2024, 1:58pm UTC](https://community.auth0.com/t/issues-with-adding-auth0-vault-connection/137355/3 "2024-07-09T13:58:46Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
