[Keycloak] TypeError: fetch failed

[JHansen2000]

Provider type

Keycloak

Environment

System:
  OS: Linux 5.14 Rocky Linux 9.4 (Blue Onyx)
  CPU: (5) x64 Intel Xeon Processor (Skylake, IBRS)
  Memory: 1.43 GB / 7.50 GB
  Container: Yes
  Shell: 5.1.8 - /bin/bash
Binaries:
  Node: 20.5.0 - ~/.nvm/versions/node/v20.5.0/bin/node
  npm: 10.8.2 - ~/.nvm/versions/node/v20.5.0/bin/npm
  pnpm: 9.6.0 - ~/.nvm/versions/node/v20.5.0/bin/pnpm
Browsers:
  Chrome: 126.0.6478.182
npmPackages:
  next: 14.2.13 => 14.2.13 
  next-auth: ^5.0.0-beta.21 => 5.0.0-beta.21 
  react: ^18 => 18.3.1 

Reproduction URL

https://github.com/JHansen2000/KeycloakAuth

Describe the issue

Keycloak Version: 25
AutJS Version: 5.0.0-beta.21

I am trying to implement a very basic Keycloak authentication flow to my app, but get the following error when attempting to sign in. Keycloak logs show no communication attempt from the application (which is obvious given the error, below).

[auth][error] TypeError: fetch failed
    at Object.fetch (node:internal/deps/undici/undici:11576:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async getAuthorizationUrl (webpack-internal:///(rsc)/./node_modules/@auth/core/lib/actions/signin/authorization-url.js:23:35)
    at async Module.signIn (webpack-internal:///(rsc)/./node_modules/@auth/core/lib/actions/signin/index.js:16:56)
    at async AuthInternal (webpack-internal:///(rsc)/./node_modules/@auth/core/lib/index.js:72:24)
    at async Auth (webpack-internal:///(rsc)/./node_modules/@auth/core/index.js:127:34)
    at async signIn (webpack-internal:///(rsc)/./node_modules/next-auth/lib/actions.js:53:17)
    at async $$ACTION_0 (webpack-internal:///(rsc)/./app/components/SignIn.tsx:39:5)
    at async /home/myuser/_dev/v2-nextjs-keycloak/nextjs-keycloak/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:39:418
    at async r_ (/home/myuser/_dev/v2-nextjs-keycloak/nextjs-keycloak/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:38:8148)
    at async r8 (/home/myuser/_dev/v2-nextjs-keycloak/nextjs-keycloak/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:41:1256)
    at async doRender (/home/myuser/_dev/v2-nextjs-keycloak/nextjs-keycloak/node_modules/next/dist/server/base-server.js:1406:30)
    at async cacheEntry.responseCache.get.routeKind (/home/myuser/_dev/v2-nextjs-keycloak/nextjs-keycloak/node_modules/next/dist/server/base-server.js:1567:28)
    at async DevServer.renderToResponseWithComponentsImpl (/home/myuser/_dev/v2-nextjs-keycloak/nextjs-keycloak/node_modules/next/dist/server/base-server.js:1475:28)
    at async DevServer.renderPageComponent (/home/myuser/_dev/v2-nextjs-keycloak/nextjs-keycloak/node_modules/next/dist/server/base-server.js:1901:24)
    at async DevServer.renderToResponseImpl (/home/myuser/_dev/v2-nextjs-keycloak/nextjs-keycloak/node_modules/next/dist/server/base-server.js:1939:32)
    at async DevServer.pipeImpl (/home/myuser/_dev/v2-nextjs-keycloak/nextjs-keycloak/node_modules/next/dist/server/base-server.js:914:25)
    at async NextNodeServer.handleCatchallRenderRequest (/home/myuser/_dev/v2-nextjs-keycloak/nextjs-keycloak/node_modules/next/dist/server/next-server.js:272:17)
    at async DevServer.handleRequestImpl (/home/myuser/_dev/v2-nextjs-keycloak/nextjs-keycloak/node_modules/next/dist/server/base-server.js:810:17)
    at async /home/myuser/_dev/v2-nextjs-keycloak/nextjs-keycloak/node_modules/next/dist/server/dev/next-dev-server.js:339:20
    at async Span.traceAsyncFn (/home/myuser/_dev/v2-nextjs-keycloak/nextjs-keycloak/node_modules/next/dist/trace/trace.js:154:20)
    at async DevServer.handleRequest (/home/myuser/_dev/v2-nextjs-keycloak/nextjs-keycloak/node_modules/next/dist/server/dev/next-dev-server.js:336:24)
    at async invokeRender (/home/myuser/_dev/v2-nextjs-keycloak/nextjs-keycloak/node_modules/next/dist/server/lib/router-server.js:173:21)
    at async handleRequest (/home/myuser/_dev/v2-nextjs-keycloak/nextjs-keycloak/node_modules/next/dist/server/lib/router-server.js:350:24)
    at async requestHandlerImpl (/home/myuser/_dev/v2-nextjs-keycloak/nextjs-keycloak/node_modules/next/dist/server/lib/router-server.js:374:13)
    at async Server.requestListener (/home/myuser/_dev/v2-nextjs-keycloak/nextjs-keycloak/node_modules/next/dist/server/lib/start-server.js:141:13)

How to reproduce

1. Clone linked Reproduction repository
2. Create a local Keycloak app (keycloak v25)

Client Id: myapp # can be whatever you want
Root URL: http://localhost:3000/
Valid Redirect URIs: http://localhost:3000/*
Web origins: *

3. Populate .env.local (see .env.template)
4. npm run dev
5. Attempt to Sign In

Expected behavior

This should navigate to the keycloak login endpoint.
I am not seeing any network traffic from the application attempting to hit the keycloak service, so whatever the issue is; it is internal to the application.

[JHansen2000]

@balazsorban44
Saw you moved this to a discussion. What suggests that this is not a bug? I've followed the Auth.JS documentation/examples and am struggling to see where I could have gone wrong reading the docs-- there's not that much to read.

Any help would be appreciated!

[balazsorban44]

https://next-auth-example.vercel.app/ has a hosted serverless example.

https://nextjs-docker-example.authjs.dev is the docker one from https://authjs.dev/getting-started/deployment
but unfortunately it's taken down from time to time as we host on Render.com and they think it's some kinda phishing site... 🤷‍♂️

Anyway, if all set up correctly, everything should work, hence the move to discussions. Otherwise the repro didn't show how keycloak was hosted, etc. might be a local connection issue.

FWIW, I'm regularly using our test keycloak instance for local development, works without any issues.

So I understand it's frustrating, but since I cannot reproduce this, it's highly unlikely a bug in Auth.js

[JHansen2000]

Thanks for your response, I'll look into the linked resources to see if I can figure something out.

What version of Keycloak are you running against locally? I'm curious if Keycloak v25 made breaking changes, so I would like to roll back to a version of Keycloak that is known to work with Auth.js. Let me know!