Infinite Redirects With Node.JS ADAL

[Captainlonate]

Hello,

This is for the Node.JS ADAL with passport, using OIDC.

I am attempting to follow the instructions on this microsoft docs page: https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-v1-openid-connect-code

My problem is that, after completing the tutorial, I'm getting infinite redirects when I attempt to access: http://localhost:3000/login

I downloaded the sample code (zip) and did an 'npm install'.

I put my client secret in config.js. Next, I put my clientId in config.js.

Then, I tried to run "node app.js", but I got this error: "Invalid value for redirectUrl.The URL must be valid and be https:// or http://"

So then I added: "redirectUrl: config.creds.returnURL," to app.js, under "new OIDCStrategy()".

Still got the same error.

So then I added "allowHttpForRedirectUrl: true," to app.js, under new OIDCStrategy({}).

Then I ran "node app.js" again, and it finally booted up and listens for requests on localhost:3000.

I tried to access localhost:3000/login in a browser, and now I'm getting infinite redirects.

Also, I've added the following Reply Urls in my Azure AD Portal: http://localhost http://localhost:3000 http://localhost:3000/ http://localhost:3000/auth/openid/return

Next I even tried changing the "returnURL" within config.js to "http://localhost:3000/". Before changing it, it was 'http://localhost:3000/auth/openid/return' by default. Neither made a difference.

I also changed responseType from 'id_token code' to 'id_token'. But, it made no difference either.

I'm still getting infinite redirects. What gives?

For Clarity, here is my what 'passport.use()' statement currently looks like:

passport.use(new OIDCStrategy({
    callbackURL: config.creds.returnURL,
    redirectUrl: config.creds.returnURL,
    realm: config.creds.realm,
    clientID: config.creds.clientID,
    clientSecret: config.creds.clientSecret,
    oidcIssuer: config.creds.issuer,
    identityMetadata: config.creds.identityMetadata,
    skipUserProfile: config.creds.skipUserProfile,
    responseType: config.creds.responseType,
    allowHttpForRedirectUrl: true,
    responseMode: config.creds.responseMode
  },

This is sort of what my config.creds looks like (obviously I redacted my clientId and clientSecret):

exports.creds = {
    returnURL: 'http://localhost:3000/',
    identityMetadata: 'https://login.microsoftonline.com/common/.well-known/openid-configuration',
    clientID: 'this-is-my-client-id',
    clientSecret: 'my-client-secret', 
    skipUserProfile: true,
    responseType: 'id_token',
    responseMode: 'query'
 };

[mike-urnun-msft]

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 85b1fba4-870b-1602-0d4f-6f50bdbfc370
• Version Independent ID: 93873b36-5f27-bd06-df23-804c38f21b37
• Content: Azure AD Node.js web app getting started
• Content Source: articles/active-directory/develop/quickstart-v1-openid-connect-code.md
• Service: active-directory
• GitHub Login: @CelesteDG
• Microsoft Alias: celested

[mike-urnun-msft]

@Captainlonate Thank you for your feedback! We will investigate and get back to you with the relevant info.

[MohitGargMSFT]

@Captainlonate Thanks for reporting. I was getting the same error using the document steps. I made below modifications in my local solution -

1. Added redirectUrl: config.creds.returnURL, in new OIDCStrategy
2. Added allowHttpForRedirectUrl: true, in new OIDCStrategy
3. Modified Step1.8 , to add reply URL in Azure Portal to http://localhost:3000/

Once, I did above change the solution in my local. I am able to run solution and login but it gives me Cannot Post/

I will assign this issue to content author to further investigate and make required changes in documented steps.

[usamamashkoor]

I am facing the same issue has anyone figured this one out...?

[CelesteDG]

@Captainlonate and @usamamashkoor - Can you please confirm that this is the quickstart that you followed: https://github.com/AzureADQuickStarts/WebApp-OpenIDConnect-NodeJS (the link in this thread should be redirecting to this now)?

CC @navyasric - This is related to the Node.js quickstart on Github

@MohitGargMSFT @SaurabhSharma-MSFT @mike-urnun-msft - Please reassign the issue to @navyasric as she owns the page on Github and can update if needed.

[jameshkramer]

@navyasric, you are the assignee for this open GitHub issue. I am investigating whether open issues should remain open and, if so, who the assignees should be. This issue has shown no activity since December of last year. Should it remain open? Are you the proper assignee; i.e. the one responsible for getting it fixed and closed?

Thank you.

Jim Kramer (v-jakram, Aquent)

[MicrosoftGuyJFlo]

please-close