This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-03-31
Channels
- # announcements (3)
- # babashka (75)
- # beginners (16)
- # calva (124)
- # cider (10)
- # clara (2)
- # clj-kondo (1)
- # cljdoc (4)
- # cljs-dev (14)
- # clojure (104)
- # clojure-australia (4)
- # clojure-czech (5)
- # clojure-europe (14)
- # clojure-germany (48)
- # clojure-nl (4)
- # clojure-serbia (4)
- # clojure-uk (34)
- # clojurescript (60)
- # community-development (16)
- # conjure (12)
- # core-async (34)
- # cursive (42)
- # data-science (7)
- # deps-new (9)
- # depstar (1)
- # emacs (11)
- # events (2)
- # fulcro (15)
- # graalvm (1)
- # inf-clojure (1)
- # jobs (3)
- # jobs-discuss (1)
- # joker (7)
- # juxt (8)
- # lsp (20)
- # malli (42)
- # meander (4)
- # off-topic (5)
- # pathom (2)
- # polylith (13)
- # re-frame (39)
- # reagent (9)
- # reitit (31)
- # releases (2)
- # rewrite-clj (23)
- # shadow-cljs (39)
- # spacemacs (11)
- # specter (6)
- # tools-deps (8)
- # xtdb (12)
About Basic Auth vs Oauth @stefan.van.den.oord and @dharrigan I worked at a local payments provider in Brazil, similar to Stripe (we inspired a lot in their APIs) and we also just choose basic auth for authentication. We never experienced any issue in two years of operation.
But there we were a focused team with a very strong DevOps practice. In the current company I work, there is an info security staff that never would approve such approach
I would rather stay away from Keycloak. It depends on your setup. But because they use the database to sync things, combined with a 'slow' database, it was quickly failing in our case.
My experience with Keycloak is that it comes with lots of operational overhead.. it is a complicated beast, and it is very likely YAGNI and it will still miss features. Although if you are willing to invest a lot of effort in operating Keycloack (like a single big installation) it might be a good option.