Attendance Security Boundaries
Summary
Attendance relies on authenticated downstream identity, presentation authorization, tenant-aware application behavior, and persistence filters.
Audience
Security engineers, backend developers, architects, QA engineers, and support engineers.
Public-safe boundary model
The service validates bearer authentication from approved identity sources and defines authorization policies at the presentation layer. Application services receive derived caller capabilities and constrain personal-versus-approver actions. Tenant context is required for mutations and drives global persistence filters. A controlled privileged context supports authorized cross-tenant administration. External Payroll calls forward the minimum authenticated tenant and correlation context needed for the dependency decision.
Audit and timeline writers record supported changes; domain events/outbox provide integration traceability. DTOs should remain minimized to use-case needs, especially because the local employee profile contains copied workforce context. Service-to-service trust depends on gateway and token validation rather than network location alone.
These controls do not establish universal assurance. New endpoints, entities, raw queries, compatibility paths, external-client failure behavior, and privileged access require security review and tenant-isolation tests. Exact credentials, claims, policy internals, fallback/bypass behavior, and exploitable failure details are intentionally excluded.
Source References
microservices/src/attendance-service/Program.csmicroservices/src/attendance-service/Api/Endpoints.csmicroservices/src/attendance-service/Application/Common/Abstractions.csmicroservices/src/attendance-service/Infrastructure/Persistence.csmicroservices/src/attendance-service/Infrastructure/PayrollLockClient.cs
Related Articles
See Also
Keywords
- Attendance Service
- Attendance Security Boundaries
Revision Information
- Status: Draft
- Last reviewed: 2026-07-15
- Review cycle: Quarterly