Hiya,
I wrote a tutorial about setting up single sign-on for NodeBB.
Full disclosure, I wrote it using my employers OAuth server (FusionAuth) as the user identity provider.
But the plugin and steps should work with any OAuth server. The plugin is here: https://github.com/FusionAuth/nodebb-plugin-fusionauth-oidc
ah, sorry, I missed that you'd linked to your github repo.
Hmmm. An easy thing to troubleshoot would be to just put console.log statements throughout your plugin. That is what I would do first, as that would narrow down the area that is causing the issue.
The oauth2 endpoints look good here: https://github.com/rgigante/nodebb-plugin-sso-oauth/blob/master/library.js
But the profile information looks a bit suspect. From git blame it looks like you didn't change that.
This page documents the profile data you'll get back, so I think you need to update the profile information extraction section.
Here's how the fusionauth plugin does this: https://github.com/FusionAuth/nodebb-plugin-fusionauth-oidc/blob/master/library.js#L91
Cheers!
Yes, the OIDC plugin is busted on 1.15. I investigated a bit, but wasn't able to find the issue. Will have to dig in more, as I do want to get to the latest version to avoid issues.
Hmmm. If I enable the oidc plugin, I see this:
"%5Bobject%20Object%5D"
as the response from https://fusionauth.io/community/forum/api/login?_=16...
Yes, the OIDC plugin is busted on 1.15. I investigated a bit, but wasn't able to find the issue. Will have to dig in more, as I do want to get to the latest version to avoid issues.
@pitaj Nope, they don't.
That makes sense as to why the login form wasn't showing up when the OIDC plugin was disabled.
Thanks!
We ended up rolling back to 1.14.x which works just fine with the OIDC plugin.
Hmmm. If I enable the oidc plugin, I see this:
"%5Bobject%20Object%5D"
as the response from https://fusionauth.io/community/forum/api/login?_=16...
It's weird because if I enable the oidc plugin ( https://github.com/FusionAuth/nodebb-plugin-fusionauth-oidc ) and then visit https://fusionauth.io/community/forum/login?local=0 then I can login just fine. It's just the default login link (/login) which is busted.
I tried to upgrade from 1.13.x to 1.15.x. I upgrade from 1.13.x to 1.14.x, and did a backup and rebuild at 1.14.x. Everything looked good. Then I upgraded to 1.15.x and now can't login.
We were using an OIDC plugin and a custom theme, but I deactivated those (and stopped, built and restarted nodebb), and I still can't login.
The screen is just blank when I click on the 'login' link.
I don't see any log messages. Here's the entire log file after a stop:
2020-11-30T22:35:21.359Z [4567/27418] - warn: You have no mongo username/password setup!
2020-11-30T22:35:21.770Z [4567/27418] - info: [socket.io] Restricting access to origin: https://fusionauth.io:*
2020-11-30T22:35:21.899Z [4567/27418] - error: [emailer] Failed to build custom email templates
Error: EACCES: permission denied, open '/var/www/forum/build/public/templates/emails/banned.js'
2020-11-30T22:35:22.230Z [4567/27418] - warn: [plugins/nodebb-theme-persona] The plugin.json field "library" is deprecated. Please use the package.json field "main" instead.
2020-11-30T22:35:22.411Z [4567/27418] - info: [api] Adding 1 route(s) to `api/v3/plugins`
2020-11-30T22:35:22.440Z [4567/27418] - info: Routes added
2020-11-30T22:35:22.451Z [4567/27418] - info: NodeBB Ready
2020-11-30T22:35:22.453Z [4567/27418] - info: Enabling 'trust proxy'
2020-11-30T22:35:22.456Z [4567/27418] - info: NodeBB is now listening on: 0.0.0.0:4567
I see no error messages in the developer tools console (I'm using an incognito window in microsoft edge and firefox).
The theme is persona at version 10.2.88.
I looked at the github issues for nodebb and in the community forum and didn't find anything about this error.
Any pointers on how to where to look next would be appreciated.
ah, sorry, I missed that you'd linked to your github repo.
Hmmm. An easy thing to troubleshoot would be to just put console.log statements throughout your plugin. That is what I would do first, as that would narrow down the area that is causing the issue.
The oauth2 endpoints look good here: https://github.com/rgigante/nodebb-plugin-sso-oauth/blob/master/library.js
But the profile information looks a bit suspect. From git blame it looks like you didn't change that.
This page documents the profile data you'll get back, so I think you need to update the profile information extraction section.
Here's how the fusionauth plugin does this: https://github.com/FusionAuth/nodebb-plugin-fusionauth-oidc/blob/master/library.js#L91
Cheers!
Hiya,
I'm a FusionAuth employee and saw this come up.
It looks like you have nodebb-plugin-sso-oauth installed, but from the github page, it looks like this is not a fully functioning plugin:
"Please note that this is not a complete plugin, but merely a skeleton with which you can create your own OAuth SSO plugin for NodeBB (and hopefully share it with others!)"
https://github.com/julianlam/nodebb-plugin-sso-oauth
It looks like you configured library.js as mentioned in the github readme? Can your share those settings changes (with anything secret obscured, of course)? Just want to make sure the config is set up correctly.
An alternative to try would be the fusionauth nodebb plugin, but it sounds like you really want the SSO plugin to work since you're planning to go to production against 10duke.
Cheers,
Dan
Hiya,
I wrote a tutorial about setting up single sign-on for NodeBB.
Full disclosure, I wrote it using my employers OAuth server (FusionAuth) as the user identity provider.
But the plugin and steps should work with any OAuth server. The plugin is here: https://github.com/FusionAuth/nodebb-plugin-fusionauth-oidc
