This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-04-25
Channels
- # architecture (4)
- # bangalore-clj (3)
- # beginners (11)
- # chestnut (1)
- # cider (24)
- # cljs-dev (14)
- # clojure (97)
- # clojure-finland (1)
- # clojure-gamedev (19)
- # clojure-italy (11)
- # clojure-nl (31)
- # clojure-norway (1)
- # clojure-uk (52)
- # clojurescript (71)
- # core-async (4)
- # cursive (60)
- # datascript (8)
- # datomic (115)
- # emacs (29)
- # figwheel (11)
- # fulcro (3)
- # garden (1)
- # hoplon (1)
- # lein-figwheel (1)
- # leiningen (7)
- # luminus (13)
- # mount (1)
- # off-topic (51)
- # onyx (31)
- # pedestal (2)
- # portkey (1)
- # re-frame (22)
- # reagent (22)
- # reitit (6)
- # remote-jobs (1)
- # schema (1)
- # shadow-cljs (73)
- # specter (2)
- # sql (1)
- # unrepl (3)
- # vim (11)
- # yada (4)
I’ve started with a fulcro app some time ago, and now have come to the point that I would like to add a login page and authentication with a jwt. I know that I can use a pre-hook on the server side to check for the token etc. But I am wondering how to go about it on the client side. I would probably add the jwt as header to all my query and mutation requests with fulcro-http-remote. And I imagine that I would have a top router that only allows the user to see the login page when they are not signed in, and routes to the ‘rest’ of the app otherwise, but I’m not sure how such a thing would be best enforced. I’d be interested to hear how others go about this, suggestions or examples are welcome 🙂