Identity and Access Component Diagram
This component diagram presents an authentication service as a set of focused software responsibilities. A client application calls the authentication API, which delegates credential checking and token issuance. Credentials are verified against a user directory. The token service evaluates policy, persists session state and records audit activity. This separation is helpful when teams need to review security boundaries and decide where to add controls such as multi-factor authentication or token revocation. The diagram is not an identity protocol sequence diagram; it shows component dependencies rather than OAuth or OpenID message exchanges. Add an external identity provider when federation is part of the real system.
Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.
Scenario
Authentication architecture
Key decisions
- Credential boundary: Separates validation from the public API.
- Token responsibility: Gives sessions and policy evaluation to the token service.
- Audit path: Records authentication activity as a separate component.
When to reuse this
Use this view to explain the major components of an authentication and access-control service.
Frequently asked questions
Why separate credential validation and token issuance?
What is the session store for?
Why include auditing?
Tweak it with chat, export PNG/SVG, or fork it for your own use case.