add Keycloak provider

[bbigras]

Reasoning 💡

Add a Keycloak provider.

I tested with a self-hosted Keycloak.

I based this PR on the auth0 provider.

I was first wondering if it was possible in #2411 (comment).

Checklist 🧢

• Documentation
• Tests
• Ready to be merged

Affected issues 🎟

Related: #1261

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/nextauthjs/next-auth/8Rrr2Nv7aWb8AipCyYN1sRcfF8si
✅ Preview: https://next-auth-git-fork-bbigras-keycloak-nextauthjs.vercel.app

[balazsorban44]

Awesome, so I assume you were able to get it to work! 🎉 I will have a closer look. From now on, I will want us to enforce stricter defaults for built-in providers for consistency, and I also want to see if we can get an account on the provider platform for testing purposes before merging. But this looks promising.

[bbigras]

so I assume you were able to get it to work!

Yep, and I just tested with please-open.it.

To reproduce:

• create client with http://localhost:3000 as the root URL
• set Access Type to confidential (the secret will be in the credentials tab after save)
• you can create a user, but when I tested it used mine as I was already logged.

KEYCLOAK_ISSUER=https://app.please-open.it/auth/realms/<realm_id>

[masone]

Apart from testing this in our stack, is there something we can do to help moving this forward?

[balazsorban44]

I just want to have a look myself before merging. Just use the source code as a custom provider if you need this already. Currently busy with migrating our adapters.

There is also a merge conflict. @bbigras could you address that please?

[bbigras]

There is also a merge conflict. @bbigras could you address that please?

@balazsorban44 Done. It seems a rebase was enough.

[codecov-commenter]

Codecov Report

Merging #2485 (5a4650d) into next (a9f699f) will decrease coverage by 0.03%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             next    #2485      +/-   ##
==========================================
- Coverage   11.52%   11.48%   -0.04%     
==========================================
  Files          84       85       +1     
  Lines        1319     1323       +4     
  Branches      378      378              
==========================================
  Hits          152      152              
- Misses        970      974       +4     
  Partials      197      197              

Impacted Files	Coverage Δ
src/providers/keycloak.js	0.00% <0.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a9f699f...5a4650d. Read the comment docs.

[balazsorban44]

Awesome, finally got around to check this out! 👍 Looks good, I only had a small comment/suggestion. Other than that, it is good to go!

[bbigras]

Done. Do you want me to squash it, or do you want to do it while merging or something?

[balazsorban44]

It's merged! Give me a sec, and I'll release it too.

Here it is: v4.0.0-next.24

[digzom]

It's merged! Give me a sec, and I'll release it too.

Here it is: v4.0.0-next.24

@balazsorban44
Is there any forecast when it can be used? Can I download this v4.0.0-next.24 release?

[balazsorban44]

Absolutely, npm install next-auth@4.0.0-next.24 😉. Make sure you don't have a caret (^) in the version number in package.json. Had a small trouble with NPM a while ago and there is a buggy 4.0.0 version out unfortunately. 😬 So you have to force the exact version above. This will be solved when we release this into stable.

Check out the migration as well: https://docs-nextauthjs.vercel.app/getting-started/upgrade-v4

[digzom]

I downloaded the version, but I was trying to use it like the previous versions. Thank you so much!