# \[Archive\] What the need of the client secret in the Web3Auth Dashboard?

**URL:** <https://builder.metamask.io/t/archive-what-the-need-of-the-client-secret-in-the-web3auth-dashboard/2395>\
**Category:** Embedded Wallets (Web3Auth)\
**Created:** [October 4, 2022, 3:59am UTC](https://builder.metamask.io/t/archive-what-the-need-of-the-client-secret-in-the-web3auth-dashboard/2395 "2022-10-04T03:59:06Z")\
**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:** [October 4, 2022, 3:59am UTC](https://builder.metamask.io/t/archive-what-the-need-of-the-client-secret-in-the-web3auth-dashboard/2395/1 "2022-10-04T03:59:06Z")

</div>

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

* * *

While making a new application, I saw two values being given in the Plug and Play section. I know the Web3Auth constructor needs a Client ID, but I never used a client secret. What's the use case for that? When should I use it? Is there a security concern about exposing my client id and client secret?

> Asked by multiple people on Telegram/ Discord channels.

  
   
 Originally posted by: [yashovardhan](https://github.com/yashovardhan)  
   
 Check the discussion at: [https://github.com/orgs/Web3Auth/discussions/671](https://github.com/orgs/Web3Auth/discussions/671)
