15
[security] Session based kong authorizer
Source: supabase/supabase#3132 · opened by @mod
This is a security enhancement,
We are using a similar Authentification mechanism with our open-source project openware/barong
But after long research we have decided to not expose the JWT and keep it behind the gateway.
We expose to the end-user a session-id or a one-time-token,
This allow to have instant and secure logout, we are also adding at the gateway level ip resolution to invalidate session,
blacklist, or maintenance page.
We would like to contribute a golang or LUA Kong plugin, which would be an optional security hardening.
Merging this would benefit both our companies.
 to Ensure Session Data is Synced with Latest User State
3 votes · 0 comments
OAuth 2.1 server: no way to require MFA (aal2) for OAuth client access tokens
1 vote · 0 comments
No comments yet.