API Limitations and Confirmation Register
Summary
The lifecycle API is Transitional. The following limitations are verified implementation boundaries, not roadmap commitments.
Audience
Engineering, QA, support, security, architecture, and product owners.
Reference Content
| Area | Verified limitation | Classification |
|---|---|---|
| Authentication | Extracted endpoints do not require the registered authentication scheme | Security review required |
| Authentication | Employee handoff forwards tenant context without workload credential | Security review required |
| Authorization | Extracted policy list is empty; native and compatibility groups apply no policy | Security review required |
| Authorization | Gateway does not authorize proxied lifecycle traffic | Implemented boundary |
| Tenant isolation | Active-onboarding lookup bypasses global filters without explicit tenant predicate | Security review required |
| Tenant isolation | Public links perform cross-tenant lookup by capability value | Requires confirmation |
| Validation | No dedicated extracted onboarding request validators | Partial |
| Validation | Checklist, document, asset, payroll, and clearance prerequisites are not enforced | Not implemented |
| Compatibility | Same route can have different security, persistence, profile, login, and error behavior | Transitional |
| Compatibility | Extracted completion consumes only part of the compatibility DTO | Partial |
| Responses | No common lifecycle response or error envelope | Transitional |
| Responses | Compatibility completion handles sensitive login-bootstrap material | Security review required |
| Employee integration | No distributed transaction or automatic reconciliation | Not implemented |
| Employee integration | Organization, manager, and location mapping is incomplete | Partial |
| Checklist | Only a generic task save/workspace boundary exists | Foundation |
| Workflow | Existing callback is requisition-only and has no required endpoint policy | Foundation/security review |
| Notifications | Exit uses internal dispatch; extracted onboarding has no verified notification HTTP boundary/resolver | Partial |
| Health | Process health does not establish dependency readiness | Foundation |
| OpenAPI | Swagger middleware exists without a curated lifecycle contract | Foundation |
| Testing | No dedicated exit, security, parity, failure-path, or UI suites found | Coverage gap |
| Versioning | No explicit API versioning, deprecation, or sunset strategy | Not implemented |
Priority confirmation themes
- Require authentication and operation-specific authorization at extracted boundaries.
- Define trusted tenant and service-identity contracts and test isolation.
- Decide compatibility parity, cutover, rollback, and retirement criteria.
- Remove or redesign sensitive completion-response behavior.
- Add offboarding, dual-target, downstream-failure, and security automation.
- Establish lifecycle versioning and OpenAPI ownership.
Source References
microservices/src/recruitment-service/Program.csmicroservices/src/recruitment-service/Api/Policies.csmicroservices/src/recruitment-service/Api/RecruitmentEndpoints.csmicroservices/src/recruitment-service/Api/RecruitmentCompatEndpoints.csmicroservices/src/recruitment-service/Infrastructure/Persistence.csmicroservices/src/recruitment-service/Infrastructure/EmployeeServiceClient.csmicroservices/src/gateway-api/Program.csControllers/RecruitmentController.csControllers/HrOperationsController.cs
Related Articles
See Also
Keywords
- API limitations
- Security review
- Compatibility risk
Revision Information
- Status: Draft
- Last reviewed: 2026-07-20
- Review cycle: Quarterly