Community

Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

How to enable SSO ( Single Sign-On ) ?

Moved Technical Support

1 Posts 1 Posters 38 Views

A Offline

A Offline
Aditya Bhardwaj229
wrote last edited by

#1

I just ran nodeBB locally. The layout and flow is different from this site ( community.nodebb.com ).

Most importantly, SSO is not there. How does one enable SSO ?

Please help. Thanks!
1 Reply Last reply
0
J julian moved this topic from NodeBB Development

Suggested Topics

S

Require users to enter email when signing up
Scheduled Pinned Locked Moved Unsolved Technical Support

3 Votes

6 Posts

376 Views

B

@waldi Which browser are you using? Does it happen on all browsers?
M

Can't find SSO settings
Scheduled Pinned Locked Moved Technical Support

0 Votes

2 Posts

511 Views

M

found it:
needs ./nodebb build needs to open dev console to flush cache
S

Cannot enable development mode with watch
Scheduled Pinned Locked Moved Technical Support

0 Votes

2 Posts

594 Views

P

@scen watch option is deprecated. Use grunt instead

https://docs.nodebb.org/en/latest/running/index.html#grunt-development
A

Problem with avatar (Twitter SSO)
Scheduled Pinned Locked Moved Technical Support twitter sso

0 Votes

2 Posts

1545 Views

W

In nodebb:

Admin > Location & APIs > SSO > Twitter > Add new api token.

In Twitter:

(User menu > Settings > API > generate SSO.
K

400 and 522 errors since enabling SSL via Nginx proxy
Scheduled Pinned Locked Moved Technical Support

1 Votes

14 Posts

10166 Views

K

Welp, I solved it.

Turns out I had the wrong directory specified in nginx for static assets. It was pointing to a different install of nodebb. For some reason that caused issues with socket.io (and only with safari/opera for some reason).

Now, here's the weird thing. I only recently started using nginx to serve the assets. Recently as in like this morning. Before that I simply had a proxy pass setup and let nodebb serve the assets. I'm not sure what was causing the 400/502 errors then but I'm just glad their solved now.