Hi,

According to the documentation I should be able to add isAuthenticated() into the middleware chain to protect routes, with an optional route to redirect to (such as to send them to sign-in).

However, I'm not seeing where that unauthorized route is ever used:

Ideally, I'd like the user to be redirected to MSAAD for sign-in if req.session.isAuthenticated is false, and I did this in my own middleware. But am I missing something that's included in this project?

Thank you!

I've got a basic app setup and when AAD goes to redirect back to my site I'm getting [ERR_INVALID_ARG_TYPE]: The first argument must be of type string or an instance of Buffer, ArrayBuffer, or Array or an Array-like Object. Received undefined
at new NodeError (node:internal/errors:371:5)
at Function.from (node:buffer:321:9)
at _callee$ (C:\Projects\myproject\node_modules\microsoft-identity-express\src\client\webapp\MsalWebAppAuthClient.ts:184:139)

any ideas?

I've done basic app setup and when AAD goes to redirect back to my site I'm getting UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'state' of undefined
at _callee$ (/home/akhilesh/Workspace/gems_re/ms-identity-javascript-nodejs-tutorial/1-Authentication/1-sign-in/App/node_modules/microsoft-identity-express/dist/microsoft-identity-express.cjs.development.js:1605:31)

any ideas?

I'm trying to create a B2C authentication solution with separate user flows for singing in and signing up for more granular control. Is it possible to utilize this library to create a separate .../sing-up handle? If so, what steps should I look to take?

Issue

This issue is for a

    - [x] question

When calling the /signin route with parameters (e.g. /signin?callingURL=https%3A%2F%2Fgoogle.com) the parameters are not passed to postLogoutRedirect. Is there any way to preserve req.qurey? I am trying to redirect the user back to the intended page (in a dynamic way) following a signin. In other words I don't want the postLogoutRedirect to be static. Thanks.