# Skip Consent Dialog for Electron App **URL:** \ **Category:** Get Help\ **Tags:** consent, application\ **Created:** [October 12, 2023, 3:21pm UTC](https://community.auth0.com/t/skip-consent-dialog-for-electron-app/118414 "2023-10-12T15:21:19Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![displagent](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/displagent/32/60163_2.png) [@displagent](https://community.auth0.com/u/displagent)\ **Post date:** [October 12, 2023, 3:21pm UTC](https://community.auth0.com/t/skip-consent-dialog-for-electron-app/118414/1 "2023-10-12T15:21:19Z")
Hi Auth0 Team, I am evidently one of the very few people on this entire platform that uses Auth0 for an Electron app. I have developed an Electron app that uses the Universal Login, and when a user signs up and creates an account, they are met with that “Allow consent…” dialog because I have to use “localhost” in my **Allowed Callback URLs** list. I used [your own Electron guide](https://auth0.com/blog/securing-electron-applications-with-openid-connect-and-oauth-2/) to set this up like a year ago. And yes, I’ve already read through [User Consent and Third-Party Applications](https://auth0.com/docs/get-started/applications/confidential-and-public-applications/user-consent-and-third-party-applications#skip-consent-for-first-party-applications). Please help me find a way to skip the “Allow consent…” dialog, it is so irritating and likely confuses my customers - I cannot stand it. Thank you for your help. ---
**Author:** ![gparascandolo](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/gparascandolo/32/38788_2.png) [@gparascandolo](https://community.auth0.com/u/gparascandolo)\ **Post date:** [October 12, 2023, 4:17pm UTC](https://community.auth0.com/t/skip-consent-dialog-for-electron-app/118414/2 "2023-10-12T16:17:22Z")
Hey @displagent 👋 Unfortunately, as the [User Consent and Third-Party Applications](https://auth0.com/docs/get-started/applications/confidential-and-public-applications/user-consent-and-third-party-applications#skip-consent-for-first-party-applications) states, Auth0 does not allow you to skip consent (even for first-party applications) if `localhost` appears in any domain in the application’s **Allowed Callback URLs** setting. For local development, you should be using a separate dev tenant. You can use the [Deploy CLI Tool](https://auth0.com/docs/deploy-monitor/deploy-cli-tool) to export/import your current tenant configuration into a new dev tenant (instead of recreating everything manually) You can also read the dangers of having `localhost` in your production tenant/application in this post: [Why localhost is not recommended as an allowed callback or origin for production?](https://community.auth0.com/t/why-localhost-is-not-recommended-as-an-allowed-callback-or-origin-for-production/46668) ---
**Author:** ![displagent](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/displagent/32/60163_2.png) [@displagent](https://community.auth0.com/u/displagent)\ **Post date:** [October 12, 2023, 4:33pm UTC](https://community.auth0.com/t/skip-consent-dialog-for-electron-app/118414/3 "2023-10-12T16:33:36Z")
That is unfortunate because, like I previously stated, [Auth0’s own Electron guide](https://auth0.com/blog/securing-electron-applications-with-openid-connect-and-oauth-2/) also encourages and requires you to use `localhost` in the **Allowed Callback URLs**. Because an Electron app is a **downloadable application existing on a client’s machine** , and not a centrally-hosted server, I see no way around requiring `localhost` to be in the **Allowed Callback URLs**. Is there some other way to make this work with Electron apps that I am not seeing? ---
**Author:** ![gparascandolo](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/gparascandolo/32/38788_2.png) [@gparascandolo](https://community.auth0.com/u/gparascandolo)\ **Post date:** [October 12, 2023, 9:48pm UTC](https://community.auth0.com/t/skip-consent-dialog-for-electron-app/118414/4 "2023-10-12T21:48:20Z")
@displagent I found this post that talks about a similar issue when `localhost` is used in Allowed Callback URLs, I hope the solution provided in the post helps 🙏 > [@Auth0 electron callback](https://community.auth0.com/t/auth0-electron-callback/72677): > > Hello community! I am trying to integrate the auth0 login flow within an electron app (electron v13.1.7). I have followed the corresponding [blog post](https://community.auth0.com/t/securing-electron-applications-with-openid-connect-and-oauth-2-0/26347), which is very useful and clear, and manage to implement the login flow for dev/testing ENVs using http://localhost/callback as the allowed callback. Moving forward Im trying to get it work with some ENVs which are more close to the users, but I am not confident about using http://localhost/callback as the allowed callback for the production app. … ---
**Author:** ![displagent](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/displagent/32/60163_2.png) [@displagent](https://community.auth0.com/u/displagent)\ **Post date:** [October 25, 2023, 4:06am UTC](https://community.auth0.com/t/skip-consent-dialog-for-electron-app/118414/5 "2023-10-25T04:06:34Z")
Thanks for trying to help @gparascandolo. It looks like this is impossible to solve in Auth0. The link provided above references a GitHub repo that states to add “file:///” to the **Allowed Callback URLs** in the Auth0 dashboard for an Electron app, but it does not work from what I can see as of 2023-10-24. Disappointing that Auth0 does not have a workaround for this. Oh well. ---
**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\ **Post date:** [November 8, 2023, 4:06am UTC](https://community.auth0.com/t/skip-consent-dialog-for-electron-app/118414/6 "2023-11-08T04:06:37Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.