Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Trying to use with keycloak-passport
See original GitHub issueI have been trying to use next-auth with this keycloak-passport Strategy. (I did have to modify the strategy’s name to be lowercase to be able to test it out)
I can log in no problem and it creates a session. Only problem is, getProfile() doesn’t seem to fire at all so the session just contains the csrfSecret but no user. Keycloak recognises I’m already logged in when trying to log in.
Have been trying to debug through what could be happening but couldn’t get to the bottom of it. Any direction on what might be the issue would be great. If I get it working would be happy to submit some documentation on it.
Issue Analytics
- State:
- Created 5 years ago
- Comments:17 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Did you solve this or have a repo that has a basic implementation of nextjs + keycloak?
You welcome! And great yes, lets close this off so it’s easy for anyone to follow if they find it when Googling in case they have the same thing. 😃 Happy to help with the separate log out issue!
The logout button code should be pretty simple, so hopefully won’t involve too much debugging.
You might want to take look at the
handleSignoutSubmit()function in the nextjs-starter project if it helps. You absolutely don’t need to set the cookie like it does, but it can be nice user behaviour (as it signs them out but keeps them on the same page).