Index of /schemas/auth/v1alpha1/

• .. (parent)
• 📁 actions/
• 📄 Group.json A named, possibly nested set of principals. Policies can be bound to groups so that permissions are granted to all members at once. Some group names are reserved, e.g. `{org}/admins` and `{org}/members` are created together with an organization. 1.2 KB
• 📄 GroupSpec.json Group specification. 595 B
• 📄 GroupSpecInput.json Group specification. 678 B
• 📄 Node.json An entire ODF deployment acting under a single identity. The node acts as a principal in system tasks and node-to-node communications and owns node-wide resources like the reserved `{node}/admins` group. 1.1 KB
• 📄 NodeSpec.json Node account specification. 505 B
• 📄 NodeSpecInput.json Node account specification. 590 B
• 📄 Organization.json An account that owns resources on behalf of a group of users but cannot authenticate or act itself. Upon creation the node creates reserved groups `{org}/admins`, whose members have owner rights over all resources of the organization, and `{org}/members`. 1.2 KB
• 📄 OrganizationSpec.json Organization account specification. 663 B
• 📄 OrganizationSpecInput.json Organization account specification. 756 B
• 📄 Policy.json A reusable grant of permissions. Policies with subject and object slots are templates instantiated via `PolicyBinding`, while policies without slots take effect on their own. 1.1 KB
• 📄 PolicyBinding.json Instantiates a `Policy` template for a concrete subject and object. 1.0 KB
• 📄 PolicyBindingSpec.json Policy binding specification. 979 B
• 📄 PolicyBindingSpecInput.json Policy binding specification. 1.0 KB
• 📄 PolicyRef.json Reference to a `Policy`. 895 B
• 📄 PolicySpec.json Policy specification. The `kind` selects the policy language. 1.8 KB
• 📄 PolicySpecInput.json Policy specification. The `kind` selects the policy language. 1.9 KB
• 📄 PrincipalHandle.json Link to a resolved identity that can act as a principal: `User`, `ServiceAccount`, or `Node`. 1.1 KB
• 📄 PrincipalRef.json Reference to an identity that can act as a principal: `User`, `ServiceAccount`, or `Node`. Short form requires a type prefix, e.g. `ServiceAccount:acme/ingest-prod`. 1.3 KB
• 📄 ResourceOwnerHandle.json Link to a resolved account that can own resources: `User`, `Organization`, or `Node`. 737 B
• 📄 ResourceOwnerRef.json Reference to an account that can own resources: `User`, `Organization`, or `Node`. Short form is the account name, as names of these accounts are unique within a node. 972 B
• 📄 ServiceAccount.json A non-human identity used by automation (scheduled flows, CI, installed applications). Service accounts are scoped under an owning account and can act as principals, but cannot own resources. 1.2 KB
• 📄 ServiceAccountSpec.json Service account specification. 529 B
• 📄 ServiceAccountSpecInput.json Service account specification. 624 B
• 📄 SubjectHandle.json Resolved reference to a party a grant is given to. 3.0 KB
• 📄 SubjectRef.json Reference to a party a grant is given to. Unlike a principal, a subject may stand for many principals at once. Short form is either a well-known subject name (e.g. `Authenticated`) or a resource reference with a type prefix, DID, or ID (e.g. `Group:acme/engineering`). 3.3 KB
• 📄 User.json An individual person who can authenticate and act as a principal. 1.0 KB
• 📄 UserSpec.json User account specification. 1.2 KB
• 📄 UserSpecInput.json User account specification. 1.2 KB