fix(09): WR-10 keep cabana's own backend guard when it is activated twice on one application

This commit is contained in:
Jakub Zych
2026-10-01 21:31:46 +02:00
parent 299d220b51
commit 2d96adf775
5 changed files with 40 additions and 2 deletions

View File

@@ -78,6 +78,7 @@ func Login(secret string) (string, error) {
| `bouncer.Registry` | Named guard registry; `bouncer.NewRegistry` creates one. |
| `bouncer.Registry.Register` | Registers a guard under a name on behalf of a plugin; duplicate names fail. |
| `bouncer.Registry.Middleware` | Returns HTTP middleware for a registered guard; unknown names fail. |
| `bouncer.Registry.Owner` | The plugin ID that registered a named guard. |
| `bouncer.NewJWTGuard` | Frontend JWT guard reading the bearer header and optional cookies. |
| `bouncer.NewBackendJWTGuard` | Admin JWT guard that requires the backend audience. |
| `bouncer.Middleware` | Standalone middleware that validates a bearer token and loads the user. |