# Skip Consent Dialog for Electron App

**URL:** <https://community.auth0.com/t/skip-consent-dialog-for-electron-app/118414>\
**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:** 1\
**Showing post:** 4

<div class="post-metadata">

**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")

</div>

@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. …

---

_[View the full topic](https://community.auth0.com/t/skip-consent-dialog-for-electron-app/118414)._
