This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-07-14
Channels
- # admin-announcements (2)
- # beginners (8)
- # boot (75)
- # clara (2)
- # cljs-dev (3)
- # cljsjs (39)
- # cljsrn (1)
- # clojure (75)
- # clojure-brasil (3)
- # clojure-dusseldorf (13)
- # clojure-gamedev (1)
- # clojure-mexico (1)
- # clojure-quebec (5)
- # clojure-russia (30)
- # clojure-sg (3)
- # clojure-spec (25)
- # clojure-uk (65)
- # clojurescript (36)
- # core-async (1)
- # cursive (15)
- # data-science (6)
- # datomic (38)
- # devcards (29)
- # editors (1)
- # emacs (11)
- # funcool (6)
- # hoplon (43)
- # immutant (48)
- # lambdaisland (2)
- # leiningen (9)
- # mental-health (4)
- # mount (1)
- # numerical-computing (1)
- # off-topic (4)
- # om (19)
- # onyx (1)
- # pedestal (1)
- # proton (1)
- # re-frame (21)
- # reagent (1)
- # specter (8)
- # sql (3)
- # testing (14)
- # untangled (9)
- # yada (31)
I’m trying to figure out how to integrate token based auth/authz with untangled-websockets, can anyone share knowledge about how I can achieve this? I’ve starred at it for awhile and it’s probably better to ask you guys before I dig in further. Thanks
@juno: @mahinshaw wrote those bits....he's out right now but I'm sure he can give you some tips when he gets back
@juno: We are using Websockets with OAuth here. So it’s likely that there is some overlap
I just added an endpoint that validaties the token, and sets cookies, which in turn get validated through our ring reqests
On the Server end we use: https://github.com/untangled-web/untangled-server/blob/master/src/untangled/server/impl/components/access_token_handler.clj to validate tokens
Cookies are set because websockets do not allow for custom headers, which is where we would have liked to put the token. The query params is also an option (albeit a less secure one) and there are hooks in untantlged-websockets for doing that.