koa-passport | Passport middleware for Koa | Application Framework library

After a bit of searching, I found that the username and password body field names are set in the passport-local package. Reference

I took some time stepping through my auth code during test runs and couldn't see any obvious problem. Then I had a thought: what if the request itself was ill formed. Turns out I was right! Inspecting the set-cookie header in the Supertest response headers I saw:

The issue was that I had initiated the Apollo Server before I applied Passport to the App. I reworked the app.ts file as per below and removed the passport parts from server.ts to get this working:

i think you need call next in callback, because koa-passport will stop call next when you provide custom callback

koa-passport

line 94: call custom callback will always call resolve(false)

line 149: if resolve(cont !== false) call next

as the result, use custom callback will stop chain. you need call next in your callback.

Looking into Webpack further we should be clear about what Webpack is and what it is used for. Webpack is front end tool, it will build front end projects and has the capability of managing tasks similar to gulp/grunt. It can be a server to serve static content. But what it is not is a full fledged back end server. You can't easily build back end API and manage complex routing. This includes things like login functionality. Instead of reinventing the wheel, use Webpack as a dev tool to easily modify and see the updated result for web design. And if you need more functionality integrate Webpack by running it in watch mode and run the back end server at the same time and setup a proxy so that Webpack will defer to the back end server for complex routing. You can use any back end technology, though Webpack is built on Common.js library so integrating it into node.js and express seems to be the easiest because they are part of a javascript ecosystem.

If I could comment I would, anyhow, I was reading through the webpack docs for the DevServer and I Think that the server is responding with the incorrect MIME type possibly because it isn't finding the bundle.js script where it is expecting it. I noticed the console output being 'http://localhost:8090/auth/bundle.js' and in the documentation the dev server expects it in the root. I think that if bundle.js is really in the auth directory that you may need to tell the server where it is with the publicPath option.

you need help function:

// @help function record route table map

According to the koa-passport docs, with v3, you should be saving your user to ctx.state.user instead of ctx.passport.user.

https://github.com/rkusa/koa-passport

I pulled down your repo and changed all references of ctx.passport to ctx.state and the /email route gives a 200 now.

I found the problem: I wasn't sending back the cookies from the client. In my fetch I had to set credentials: 'include' to make it work and since I am using koa-cors, I had to specify to allow cookies as well.