Package com.cloudforge.core.manager.auth
package com.cloudforge.core.manager.auth
-
ClassDescriptionA CloudForge Manager user-directory account, as seen through
AuthBackend— a typed stand-in for what used to be an ad-hocMap<String,Object>built by hand in two different shapes (one for local rows, one for Cognito pool users).Request to create a new account viaAuthBackend.createAccount(AuthAccountRequest).Partial update forAuthBackend.updateAccount(String, AuthAccountUpdate)— every field isnull/unset unless the caller means to change it (no "clear this field" sentinel is needed; every field here is meaningful when present and skipped when absent, matching the semantics of theMap<String,Object> body-based updates this replaced).CloudForge Manager's Users-page CRUD, abstracted over whichever directory of accounts is currently authoritative — the local H2/Postgres DB, or an AWS Cognito User Pool.Marks a CloudForge Manager REST controller method as requiring only that the caller pass Manager's baseline access check — no specificpolicyand no resolvedcaller identitybeyond that.Marks a CloudForge Manager REST controller method as requiring the caller hold a privileged role (admin/manager) or theoperations:runpolicy — the same bar destructive/high-blast-radius operations have always used, distinct from a single namedpolicy.Marks a CloudForge Manager REST controller method as requiring a resolved caller identity, but no specificpolicycheck beyond being authenticated — self-service endpoints where the caller acts on their own account/resources use this (e.g.Marks a CloudForge Manager REST controller method as requiring a resolved caller who is permitted the named policy.Strategy interface for where Manager's own session cookies live — sibling toAuthBackend(local-DB-vs-Cognito for the *user directory*; this is in-memory-vs-Redis for *which session cookies this process currently recognizes*, an orthogonal concern).