# \[Archive\] Web3Auth: Custom Auth Verifier URL Modification

**URL:** <https://builder.metamask.io/t/archive-web3auth-custom-auth-verifier-url-modification/2274>\
**Category:** Embedded Wallets (Web3Auth)\
**Created:** [December 7, 2022, 5:54am UTC](https://builder.metamask.io/t/archive-web3auth-custom-auth-verifier-url-modification/2274 "2022-12-07T05:54:01Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![githubdiscussions](https://avatars.discourse-cdn.com/v4/letter/g/13edae/32.png) [@githubdiscussions](https://builder.metamask.io/u/githubdiscussions)\
**Post date:** [December 7, 2022, 5:54am UTC](https://builder.metamask.io/t/archive-web3auth-custom-auth-verifier-url-modification/2274/1 "2022-12-07T05:54:01Z")

</div>

> **🏛 Archived Content from Web3Auth Community**
> 
> This topic was originally posted by **githubdiscussions** on 12/7/2022.  
> This content has been migrated from our previous community forum to preserve valuable discussions.

* * *

Is it possible to change the JWKs callback url location (Assuming is exactly the same JWKs)?  
Or if I recreate the verifier with a same name and a different verifier will my users still be able to access to their existing wallets?

  
   
 Originally posted by: [kevinrodriguez-io](https://github.com/kevinrodriguez-io)  
   
 Check the discussion at: [https://github.com/orgs/Web3Auth/discussions/1023](https://github.com/orgs/Web3Auth/discussions/1023)