# "id\_token not present in TokenSet" error on /login with screen\_hint = signup

**URL:** <https://community.auth0.com/t/id-token-not-present-in-tokenset-error-on-login-with-screen-hint-signup/75668>\
**Category:** Get Help\
**Tags:** signup, id\_token, login, auth0\
**Created:** [December 31, 2021, 1:55pm UTC](https://community.auth0.com/t/id-token-not-present-in-tokenset-error-on-login-with-screen-hint-signup/75668 "2021-12-31T13:55:25Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jonpawelko](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jonpawelko/32/33352_2.png) [@jonpawelko](https://community.auth0.com/u/jonpawelko)\
**Post date:** [December 31, 2021, 1:55pm UTC](https://community.auth0.com/t/id-token-not-present-in-tokenset-error-on-login-with-screen-hint-signup/75668/1 "2021-12-31T13:55:25Z")

</div>

My application worked 100% fine running on Localhost3000, but when I moved my NodeJS server to a hosted platform on Digital Ocean I started receiving the “id\_token not present in TokenSet” when I try to login using screen\_hint = ‘signup’ (Registering for my site). The login functionality works fine on the remote server when I logged in as a user already in Auth0, but when I try to register a new user, the actual registration works (The ID is created in Auth0), but the redirect doesn’t work anymore and I get the id\_token set error instead of returning to my app.

It appears all of the help on this topic is specific to the /authorize api call, which I’m NOT using. Is it mandatory to use /authorize instead of /login now that I have a remote Node JS server? If it is possible to still use /login, do I need to set the parameters specifically on the login call with screen\_hint = signup? Or do I need to set the parameters on the original Auth0 config use call? I would like to keep a simple approach and not use addl tokens if possible. Thanks!

I tried many combinations of the AuthorizationParams, but nothing seems to change my result…

response\_type: “id\_token”,  
response\_mode: “form\_post”,  
scope: “openid profile email”

response\_type: ‘code’,  
scope: ‘openid profile email’,

I have included my original code that worked on Localhost3000:

// ---- Original Code --------------------------------

const { auth } = require(‘express-openid-connect’);

const config = {  
authRequired: false,  
auth0Logout: true,  
secret: ‘kjgfkjwehrasrjbadjbjhsdfjbsdfgjak9kb2agknxxxxx’, // changed  
baseURL: ‘[http://159.65.180.75](http://159.65.180.75)’,  
clientID: ‘xILNWHiJzCD9MOOltuo391jUROB7Al0Q’,  
issuerBaseURL: ‘[https://dev-ae79isjb.us.auth0.com](https://dev-ae79isjb.us.auth0.com)’  
};

app.use(auth(config));

// — later on, I register --------

res.oidc.login({  
returnTo: ‘/callback’,  
authorizationParams: {  
screen\_hint: ‘signup’  
},  
});

// ----- End original code -----------------------------------------

---

<div class="post-metadata">

**Author:** ![rueben.tiow](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/rueben.tiow/32/11646_2.png) [@rueben.tiow](https://community.auth0.com/u/rueben.tiow)\
**Post date:** [January 11, 2022, 6:43pm UTC](https://community.auth0.com/t/id-token-not-present-in-tokenset-error-on-login-with-screen-hint-signup/75668/2 "2022-01-11T18:43:36Z")

</div>

Hi @jonpawelko,

Thanks for reaching out to the Auth0 Community!

I understand you encountered issues with your app, specifically with the _“id\_token not present in TokenSet”_ error.

I will follow up with you on DM to further assist you.

Thanks!

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [January 26, 2022, 6:44pm UTC](https://community.auth0.com/t/id-token-not-present-in-tokenset-error-on-login-with-screen-hint-signup/75668/3 "2022-01-26T18:44:28Z")

</div>

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.
