OAuth 2 / OpenID Connect Backend-For-Frontend. It mediates between browser
SPAs and an identity provider (Keycloak, Google, …) so the SPA never handles
raw tokens: they are kept server-side and the browser only gets an httpOnly
cookie. It offers two ways in: /auth/login (the password grant, from the
SPA’s own form, which is what gui_agent and gui_treedb use) and /auth/callback
(the authorization-code flow with PKCE). The
OAuth2 / BFF guide has the whole contract.
Architecture¶
C_AUTH_BFF_YUNO (default service)
__bff_side__ : gate of per-connection C_AUTH_BFF instancesThe yuno (C_AUTH_BFF_YUNO) hosts a __bff_side__ gate. Each client
connection gets its own C_AUTH_BFF gobj that drives the OIDC round-trip with
the IdP. The protocol/flow details live in the Auth, permissions, TLS
chapter.
Commands¶
| Command | Description |
|---|---|
view-bff-status | Snapshot of every C_AUTH_BFF instance: queues, pending tasks, active IdP round-trip |
help | Command help |
Deep dive¶
See Auth, permissions, TLS for the
full OIDC / auth_bff flow, C_AUTHZ, the cookie model and cert-sync.