Does NodeBB provide support for a user database other than the one it builds in mongo? How would I integrate NodeBB with Keycloak?
-
Hi again.. I just realized that the two client protocols supported by Keycloak are SAML, and OpenID Connect.
Not sure the OAuth2 plugin that you pointed me to aligns with either of these protocols... Thoughts?
-
@David-Sargrad OIDC connect is OAuth2, so yes
There may be differences, but I'm talking in general
The plugin also supports the discovery URL, so just paste the provider domain and the plugin might even auto populated some of the other fields
-
I see.. the plugin settings within the ACL?
-
As an aside, i can set breakpoints in nodebb.. if it helps in verfiying function..
-
Trying to figure out where I can set the provider settings.. Interestingly I see a "Multiple OAuth2" option under Social Authentication. But when I click on it, it doesnt give me options to set.
-
-
One of the screenshots shows Node.js 16 in use and Node.js 18 or 20 is required.
https://community.nodebb.org/topic/17723/nodebb-3-6-0-minimum-nodejs-version -
hmm.. ok.. ty
-
nodebb build now gives me an options menu
-
do i really need to migrate to node 18 or 20.. it seems that things are working
-
ty.. at some point we will absolutely move to 18 or 20.. but im hoping to make progress with 16 for now.
-
so it seems like i can define a provider now.. Not sure how to set this. I'll consult with some guys internally to see what i can learn about an "OAuth2 endpoint" exposed by Keycloak.
-
Do I need full URL's in the following?
Are fields like the authorization url required? Is the client secret required? We do have a client id that has a secret.
What looks wrong in the following? I get an "invalid data" message when I attempt to confirm.
-
Do I need full URL's in the following?
Are fields like the authorization url required? Is the client secret required? We do have a client id that has a secret.
What looks wrong in the following? I get an "invalid data" message when I attempt to confirm.
Apparently the client secret is required.
-
I was able to get to the Keycloak login prompt:
However the following failure occurs when I login.
Currently using this configuration:
Looking in keycloak, it did create a session for that login
-
The username is "dave1".. the email is a fake email: [email protected]