Absinthe Authentication
summary
Adds authentication by inserting a plug before Absinthe that extracts credentials (e.g. Authorization header or parsed JWT) and writes a map into conn.private.absinthe context, e.g. %{current_user: user} or %{current_user: nil} for guests, instead of relying on HTTP status codes. Resolvers receive the context as their second arg and can pattern-match in resolvers to allow public fields, return errors for protected ones, or grant admin-only data. This is simple, per-field authorization that actually works.
AI-written summary · about
related talks
40mAuthentication and Authorization in GraphQL
27mAuthorization in the GraphQL era
10mOverview of Authentication and Authorization Features in Envoy
33mFirst-Class Auth Experience In Frontend Applications
33mAuthenticate and authorize users “your way” when they access your appl & platf
37mLeveraging Cryptographic Lineage for Context and ConnectedTrust
05mLT: Zero to Auth in 60 Seconds
13mMagic Authentication, The Missing LEGO Piece