19 docs tagged with "rbac"

Understand how user accounts are organized in cidaas.

cidaas provides fine-grained authorization beyond OAuth2 scopes and group/role restrictions through the OpenID AuthZEN standard. AuthZEN separates policy administration from policy decision and supports attribute-based policies (Rego/OPA), external data via Policy Information Points (PIP), and Relationship-Based Access Control (ReBAC).

Learn how to create users in cidaas with admin-set passwords, including role requirements, API integration, user flow, and webhook events.

Overview

Learn how to delete users in cidaas, including scheduled deletion, immediate deletion, GDPR compliance, webhook events, and API integration.

Configure how long changelog and user-activity events are kept in cidaas before they are removed.

Group Role Restriction in cidaas — control who can log in by verifying group membership and roles, embed hints in the JWT, and validate access at runtime.

Learn how to invite users in cidaas, including email templates, invitation states, API integration, and the complete invitation flow.

cidaas supports LDAP (Lightweight Directory Access Protocol) and Active Directory for authentication and user synchronization. You can configure cidaas to act as an Identity Provider (IdP) or as a Service Provider (SP).

Permission management in cidaas — scopes, roles, groups, group/role restrictions, AuthZEN, and group selection, configured in Trustdesk.

cidaas ReBAC uses Relation Store to store authorization graphs: object types, relations, permissions, and relationship tuples.

Learn how to implement self-service user registration in cidaas, including webfinger user existence checks, invitation-based registration, and the complete registration flow.

Hosted page

Learn how to update user profile information in cidaas, including field permissions, instant email/mobile changes, and API usage.

cidaas User Management provides capabilities for creating, managing, and organizing user accounts. This guide introduces core concepts and workflows.

To allow and restrict access to the features of your applications, every user must be assigned permissions based on their role (defines what they can do and not do on your app).

Configure registration and login field profiles in cidaas (User Setup), link them to applications via user_setup_id, and manage profiles through Trustdesk or the User Setup API.

Learn how to manage user status in cidaas, including status values, transitions, API usage, email templates, and webhooks.

After an authentication, cidaas approves the correctness of provided information with a token. OAuth2 and OpenID Connect work with different tokens. Either way, cidaas will provide an access token based on OAuth2 standard. The token is built up as a JWT (JSON Web Token), which is essentially a base64-encoded JSON format. Optionally, in a user authentication, cidaas can also provide an ID token, which is based on OIDC standard and also built up as a JWT.