# \#passport

**URL:** https://community.auth0.com/tag/passport/121.md

[Latest](https://community.auth0.com/latest.md) · [Categories](https://community.auth0.com/categories.md) · [Tags](https://community.auth0.com/tags.md)

---

## [Login in production not working](https://community.auth0.com/t/login-in-production-not-working/39057)

<div class="topic-metadata">

**Author:** [@ikemnomso](https://community.auth0.com/u/ikemnomso)\
**Replies:** 7\
**Last updated:** [January 14, 2023, 1:14am UTC](https://community.auth0.com/t/login-in-production-not-working/39057 "2023-01-14T01:14:42Z")

</div>

I’m trying to deploy my nodes app on Heroku. I can login in locally but on the deployed app, after clicking login it just loops back to the login page. My Auth0 log shows Successful login but the app doesn’t redirect to …

---

## [How to pass audience in passport-auth0 strategy?](https://community.auth0.com/t/how-to-pass-audience-in-passport-auth0-strategy/84551)

<div class="topic-metadata">

**Author:** [@Frederic.Meriot](https://community.auth0.com/u/Frederic.Meriot)\
**Replies:** 1\
**Last updated:** [June 3, 2022, 6:18pm UTC](https://community.auth0.com/t/how-to-pass-audience-in-passport-auth0-strategy/84551 "2022-06-03T18:18:50Z")

</div>

Hi, I’am using NestJS 8 with passport-auth0. I don’t know how to pass an audience to the strategy to obtain a JWT access-token (instead an opaque one). I’am using this strategy : @Injectable() export class Auth0Strateg…

---

## [Auth0 React, Node, & Passport - session.passport.user undefined](https://community.auth0.com/t/auth0-react-node-passport-session-passport-user-undefined/59146)

<div class="topic-metadata">

**Author:** [@blubberbo](https://community.auth0.com/u/blubberbo)\
**Replies:** 2\
**Last updated:** [March 25, 2021, 10:01am UTC](https://community.auth0.com/t/auth0-react-node-passport-session-passport-user-undefined/59146 "2021-03-25T10:01:11Z")

</div>

Hi, I have inherited an app that I am trying to get to work and having trouble. The app uses React, Node, and Passport. My understanding of the workflow is as follows: user clicks “login” in the React app React calls …

---

## [Forwarding callback request to the API causes TokenError](https://community.auth0.com/t/forwarding-callback-request-to-the-api-causes-tokenerror/29283)

<div class="topic-metadata">

**Author:** [@michaelfarnik](https://community.auth0.com/u/michaelfarnik)\
**Replies:** 1\
**Last updated:** [February 8, 2021, 10:07pm UTC](https://community.auth0.com/t/forwarding-callback-request-to-the-api-causes-tokenerror/29283 "2021-02-08T22:07:32Z")

</div>

My Auth0 setup was working fine but then I found out it wasn’t suitable for production. The problem was that the front end and back end are on the same domain so when Auth0 redirected the user to the callback, the front …

---

## [Pass authorization params with Express/Passport](https://community.auth0.com/t/pass-authorization-params-with-express-passport/46375)

<div class="topic-metadata">

**Author:** [@themadhatter](https://community.auth0.com/u/themadhatter)\
**Replies:** 1\
**Last updated:** [July 16, 2020, 10:15pm UTC](https://community.auth0.com/t/pass-authorization-params-with-express-passport/46375 "2020-07-16T22:15:44Z")

</div>

I have an Express app that uses Passport with the auth0 strategy. I’m trying to have 2 different endpoints for /login and /signup and would like the initial screen to be different depending on the the route the user acce…

---

## [Getting "Unable to configure verification page" when trying to integrate with React Native](https://community.auth0.com/t/getting-unable-to-configure-verification-page-when-trying-to-integrate-with-react-native/38601)

<div class="topic-metadata">

**Author:** [@michaelfarnik](https://community.auth0.com/u/michaelfarnik)\
**Replies:** 0\
**Last updated:** [February 27, 2020, 5:34pm UTC](https://community.auth0.com/t/getting-unable-to-configure-verification-page-when-trying-to-integrate-with-react-native/38601 "2020-02-27T17:34:27Z")

</div>

Hey, We built a web app a while ago which uses Auth0 Lock on the front end and Passport.js on the back end for authentication. It works fine and we’re now building a companion React Native app that would connect to the …

---

## [Chrome for Android and add to home screen functionality](https://community.auth0.com/t/chrome-for-android-and-add-to-home-screen-functionality/8490)

<div class="topic-metadata">

**Author:** [@gorbypark](https://community.auth0.com/u/gorbypark)\
**Replies:** 1\
**Last updated:** [November 3, 2017, 4:26pm UTC](https://community.auth0.com/t/chrome-for-android-and-add-to-home-screen-functionality/8490 "2017-11-03T16:26:54Z")

</div>

Recently, something appears to have changed in the latest version of Chrome for Android that causes all users who try to log in from an icon on their home screen (that was added using the ‘add to home screen’ functionali…

---

## [How do we customise the login screen when using passport-auth0](https://community.auth0.com/t/how-do-we-customise-the-login-screen-when-using-passport-auth0/6973)

<div class="topic-metadata">

**Author:** [@alt](https://community.auth0.com/u/alt)\
**Replies:** 3\
**Last updated:** [November 1, 2017, 9:12pm UTC](https://community.auth0.com/t/how-do-we-customise-the-login-screen-when-using-passport-auth0/6973 "2017-11-01T21:12:22Z")

</div>

I have a nodejs application using passport-auth0 as the login strategy How do I customise the login/signup form? I’ve tried sending the same options as Lock.js take but to no avail.

---

## [PassportJS + Browsersync's External url Throws Error](https://community.auth0.com/t/passportjs-browsersyncs-external-url-throws-error/6688)

<div class="topic-metadata">

**Author:** [@yousef.shanawany](https://community.auth0.com/u/yousef.shanawany)\
**Replies:** 1\
**Last updated:** [May 22, 2017, 9:45pm UTC](https://community.auth0.com/t/passportjs-browsersyncs-external-url-throws-error/6688 "2017-05-22T21:45:50Z")

</div>

I’m having a bad experience with PassportJS running with Browser-sync. I’m using passport-Auth0 with my expressjs application. My app runs on localhost:1337. Browser-sync proxies that and runs its version on localhost:30…
