Development edition · 16 November 2026. Commands using repository paths, Make targets or sample projects require access to the Quinzee source checkout. No public installer is available. Examples use disposable local environments.
21. Give applications and people the right identity
An app registration describes a client or API. Its service principal is the application's identity inside the local tenant. A managed identity is a service principal whose credentials the hosting environment supplies. A user is a person who can authenticate interactively. A group connects a set of users to grants. AAD, Azure AD and Microsoft Entra ID are names for the identity technology; they do not describe three separate databases in Quinzee.
Use a fresh development group and synthetic accounts in this lesson. Start with the bootstrap identity to register and assign objects, then run the application with the restricted identity you created. Keep those two roles separate.
Manage identities in QHQ
Connect QHQ with your environment's bootstrap credentials. Expand Azure / Entra ID in the navigation. Every form uses the same public HTTPS APIs as clients. Use Browse to select an object, then Create / Edit to change it. Save updates the selection; Create makes a new object. Deleting requires the confirmation checkbox. Refresh after changing records through another client.
- In Users, enter a display name, username such as
alice@example.test, and a password of at least 12 characters; choose Create. Select a user to rename, enable/disable, reset the password or delete it. Password input clears after submission. - In Groups, create a security group with a display name and stable group account name. Select it, open Members, choose a user or group, and use Add member or Remove member. Browse shows the current member IDs. Cycles are rejected.
- In App registrations, create a display name and exact redirect URI. Select Public client for an interactive client without a secret. Select Expose API for an API that will issue application roles. The local Application enabled switch controls this emulator's sign-in policy.
- Select a registration and open Credentials to add a secret. Copy the one-time value into private application configuration; it cannot be retrieved later. Refresh lists credential IDs for removal. Public clients need no secret.
- In Enterprise applications, choose the app registration and create its service principal. This is the tenant identity used for assignments. Select it to edit its display name, sign-in status or Require an app role assignment.
- In App roles, choose a registration in Browse, then define a role in
Create / Edit, for example
Orders.Read. Choose whether users/groups, applications, or both may receive it. Disable a role and remove its assignments before deleting the definition. - In App role assignments, choose the target Enterprise application in Browse. In Create / Edit choose a user, group or service principal and role, then Create. Group assignments grant roles to direct user members only; nested membership does not grant application roles.
Under Azure / Resource access, Managed identities creates standalone user-assigned identities in a resource group. Role assignments assigns a resource role at the entered subscription, resource-group or resource scope. Choose a principal and role, then Create. Group-based RBAC includes nested user membership. App roles and Azure resource roles are independent; neither grants directory administration.
Under Windows / Directory, LDAP directory shows the shared backend and listener status and links to the same Users and Groups. LDAP clients can use the POSIX view or the Windows-oriented user/group view. This module does not implement Windows domain join or Kerberos. Configure PostgreSQL and OpenLDAP using the instructions below before connecting LDAP clients.
Emulator → Modules lists each Azure/Windows frontend separately, including its dependencies. Unloading a frontend preserves records in the shared identity authority. The labels describe the API family; they do not indicate a connection to a Microsoft cloud tenant. Full cloud integration remains separate work.