nodebb-plugin-sso-facebook issue

Technical Support
  • Hello, I have installed the nodebb-plugin-sso-facebook via npm and when I have configured it I have saved it without having a password. Now if I try to start up my nodebb I am getting the following error and I cannot back to enter the password.

    18/12 09:37 [5531] - error: TypeError: OAuth2Strategy requires a clientSecret option
        at Strategy.OAuth2Strategy (/var/www/html/NodeBB/node_modules/nodebb-plugin-sso-facebook/node_modules/passport-    facebook/node_modules/passport-oauth2/lib/strategy.js:84:38)
        at new Strategy (/var/www/html/NodeBB/node_modules/nodebb-plugin-sso-facebook/node_modules/passport-facebook/lib/strategy.js:55:18)
        at Object.Facebook.getStrategy (/var/www/html/NodeBB/node_modules/nodebb-plugin-sso-facebook/library.js:56:17)
        at /var/www/html/NodeBB/node_modules/nodebb-plugin-sso-facebook/library.js:51:14
        at /var/www/html/NodeBB/node_modules/nodebb-plugin-sso-facebook/library.js:44:4
        at /var/www/html/NodeBB/src/meta/settings.js:12:4
        at try_callback (/var/www/html/NodeBB/node_modules/redis/index.js:573:9)
        at RedisClient.return_reply (/var/www/html/NodeBB/node_modules/redis/index.js:661:13)
        at ReplyParser.<anonymous> (/var/www/html/NodeBB/node_modules/redis/index.js:309:14)
        at ReplyParser.EventEmitter.emit (events.js:95:17)
    [cluster] Child Process (5531) has exited (code: 1, signal: null)

    Is there any way I can reset the configuration of the plugin so that I can have again empty fields?

  • The plugin shouldn't actually start without those values, so that's a bug. In the meantime:

    ./nodebb reset -p nodebb-plugin-sso-facebook will disable the plugin.

  • I tried that. then when I have activated and reloaded the plugin the nodebb quit with the error above.

  • @Peter-Zoltan-Keresztes reset the plugin again using ./nodebb reset -p nodebb-plugin-sso-facebook

    Restart NodeBB.... Go to ACP -> Plugins page and uninstall it from there. Reload NodeBB and install it again (better to do from ACP again)

  • @pichalite This time, it was actually a bug 😄

    @Peter-Zoltan-Keresztes Resolved in v1.1.7

  • @julian I confirm. It is fixed.

Suggested Topics