I think I managed to find the solution to your issue @gorgiselkov I'm guessing you're using IIS but if not it might help as well. Here: https://community.nodebb.org/post/72229

@julian So my site receives "https$mysite$site$com/auth/auth0/callback?code=letternumberjumble&state=letternumbersymboljumble" and responds with a 500. while their site gets "https$forum$antergos$com/auth/auth0/callback?code=letternumberjumble" $ being replaced with the obvious things because the spam defense doesn't let me post things that seem like links yet. If I remove the state I can at least get some better feedback from the backend, though it complains the callback code is wrong (probably because it needs to happen in that first response directly, at least I assume it shouldn't work if merely resent/spoofed later). 2018-05-01T15:30:53.594Z [26584] - error: /auth/auth0/callback TokenError: Invalid authorization code at Strategy.OAuth2Strategy.parseErrorResponse (/data/node_BB/nodebb/node_modules/passport-oauth2/lib/strategy.js:329:12) at Strategy.OAuth2Strategy._createOAuthError (/data/node_BB/nodebb/node_modules/passport-oauth2/lib/strategy.js:376:16) at /data/node_BB/nodebb/node_modules/passport-oauth2/lib/strategy.js:166:45 at /data/node_BB/nodebb/node_modules/oauth/lib/oauth2.js:191:18 at passBackControl (/data/node_BB/nodebb/node_modules/oauth/lib/oauth2.js:132:9) at IncomingMessage.<anonymous> (/data/node_BB/nodebb/node_modules/oauth/lib/oauth2.js:157:7) at emitNone (events.js:111:20) at IncomingMessage.emit (events.js:208:7) at endReadableNT (_stream_readable.js:1064:12) at _combinedTickCallback (internal/process/next_tick.js:138:11) at process._tickCallback (internal/process/next_tick.js:180:9) Don't spend time on it for now, I'll see if I can use a rule on the auth0 site to not send back the state and I'll report back if that works or not.

Is there any progress on this, as I am also interested in using Drupal with NodeBB.

@livey0u It is just a requirejs module so just require it. require(['components'], function (components) { components.get('user/logout').off('click').on('click', function() { // your custom behaviour here }); });

I apologize for such a dirty job.

I'd add some client side code that checks for the cookie existing, and react (redirect) appropriately

Finaly managed to fix 502, needed to use node v4 instead of v6. Still having an issue with this plugin when i try to login : Registration Error int-steam-unexpected-error

In nodebb: Admin > Location & APIs > SSO > Twitter > Add new api token. In Twitter: (User menu > Settings > API > generate SSO.

As an addendum, I'm not going to lie, configuring an OAuth2 provider is rage-inducing. You may want to consider a "login-override" instead, which would allow you to verify user credentials via the username/password login box on NodeBB, effectively bypassing NodeBB's username/password check in favour of your own:

@Macrow-Willson , ah setup: apache,debian,mod_proxy

@pichalite I am still confused that. it need update after install. But our node_module files always in ignore... so I don't thinks it's a good way to put plugs into node_module....

i also added this code to load default preferences (inside the "success" function when creating a new user) User.setSetting(uid, 'dailyDigestFreq', 'week', null); User.setSetting(uid, 'notificationSounds', 1, null); User.setSetting(uid, 'followTopicsOnCreate', 1, null); User.setSetting(uid, 'followTopicsOnReply', 1, null); User.setSetting(uid, 'sendChatNotifications', 1, null);

Yay, another entry into the contest