Testing Security and Access Controls
A developer wants to verify application behaviour under different permissions.
Intermediate · Developer, Administrator · Documented building blocks
Scenario overview; the standalone tutorial and its executable artifacts are not yet published. Start with the linked book exercises, which document the existing building blocks.
What Quinzee contributes
The bounded permission model makes those specific authorization checks inspectable.
The proposed example
Create separate local principals and exercise allowed and denied ARM or Service Bus requests at supported scopes.
Required capabilities
Local identities and supported scoped ARM/Service Bus roles; PostgreSQL/OpenLDAP for LDAP.
Boundaries and remaining work
No MFA, federation, full Graph or other data-plane RBAC. LDAP is read/authenticate only; no Kerberos or domain join.
What to verify
- Use a non-bootstrap principal for denial tests.
- Do not treat stored policy properties as enforcement on unsupported data planes.
Read the three perspectives
- The Book of Quinzee: Sign in and create a resource group
- The Book of Quinzee: Give applications and people the right identity
- Quinzee Administrator’s Guide: Operate the shared Entra and LDAP directory · Primary reference
- Quinzee Internals: TLS, identity and DNS
- Quinzee Internals: One directory behind HTTPS and LDAP