I’m writing a plugin to enable shared cookie SSO with a bespoke system, but I’m not sure how to let the Ember fronted know that a user has ‘logged in’ in this way. I’ve subclassed Auth::DefaultCurrentUserProvider and extended current_user to check for our shared cookie if the super method hasn’t fo…

Why are you not using the built in SSO support? [이미지] Setup DiscourseConnect - Official Single-Sign-On for Discourse (sso) Integrations DiscourseConnect is a core Discourse feature that allows you to configure “Single Sign-On (SSO)” to completely outsource all…

I wish I could, but IIRC, the built-in SSO uses OAuth/OIDC. The bespoke service I’ve got to integrate with doesn’t implement OAuth, so they want me to grab the cookies and call an endpoint which will give me the user’s profile.

[이미지] edL: I wish I could, but IIRC, the built-in SSO uses OAuth/OIDC. The built-in Discourse SSO does not use OAuth/OIDC. It does require you to add some code to your SSO provider site to handle SSO requests from Discourse. There are quite a few existing implementations of this that you can …

Ok, I’ve had another look, and I see what you mean. It shouldn’t be too hard to implement an SSO endpoint. However, before chucking it over the fence and making work for them, can I confirm whether the shared cookie approach could also be viable? It feels like I’m very close (loading the forums on…

The best solution here is to properly implement SSO. If you do want to keep trying with the shared cookie, you can refresh the browser of a specific user using something like this integrated into your plugin: MessageBus.publish "/file-change", ["refresh"], user_ids: [user.id] I think this will re…

Hmm.. that’s really interesting – thanks. That’s exactly the sort of thing I was looking for, although having to specify a user is a catch 22. If there’s no logged in session in Ember, then it’s not going to know to respond to the message for a specific user id. I’ll see if we can use the standard …

[이미지] edL: If there’s no logged in session in Ember The messagebus makes a fresh request every 30 seconds, so it should pick up the user-id, even if the rest of the Ember app does not. [이미지] edL: I’ll see if we can use the standard SSO instead. :+1: definitely the safer option here

Shared cookie SSO: Notifying frontend

개발

codinghorror (Jeff Atwood) 6월 12, 2019, 1:55오후 2

Why are you not using the built in SSO support?

글		댓글	조회수
Issues using SSO in custom web app Development	10	1550	1월 9, 2018
Cookie Based Authentication in discourse via Plugin SSO	6	2267	9월 5, 2018
Automatic session management with OAuth SSO SSO	5	2062	10월 14, 2020
Detecting user already logged in when using SSO Feature sso , discourseconnect	10	5574	11월 5, 2016
Discourse login by cookie token SSO	2	1318	5월 23, 2022

Shared cookie SSO: Notifying frontend

Related topics