Workflow HTTP Boundaries
Summary
One Recruitment workflow callback is verified, but it handles job-requisition approval only. No onboarding approval, checklist orchestration, exit approval, clearance, or access-revoke workflow callback was found.
Audience
Developers, QA, support, security reviewers, and solution architects.
Callback flow
Verified callback behavior
The callback is always mapped even when workflow integration is disabled. It validates the terminal decision, optional subject type, tenant context, and requisition resolution. Duplicate callbacks for an already-decided requisition are acknowledged without creating another job opening. Optional live-state verification can be enabled.
Security boundary
The callback has no required endpoint authorization metadata. It requires tenant context through the command. This is an adjacent security concern because the operation changes requisition state even though it is not a lifecycle callback.
Not implemented for lifecycle
- Onboarding approval callback
- Checklist task callbacks
- Employee-initialization workflow callback
- Exit decision callback
- Asset or payroll clearance callback
- Notification-delivery callback tied to lifecycle state
Requires confirmation
- Caller authentication and authorization for the existing requisition callback.
- Whether lifecycle orchestration belongs in Workflow Service.
- Callback signature, replay protection, delivery retry, and audit requirements.
Source References
microservices/src/recruitment-service/Api/RecruitmentEndpoints.csmicroservices/src/recruitment-service/Application/WorkflowIntegration.csmicroservices/src/recruitment-service/Application/Commands/RequisitionCommands.csmicroservices/src/recruitment-service/Infrastructure/WorkflowServiceClient.csmicroservices/src/recruitment-service/Program.cs
Related Articles
See Also
Keywords
- Workflow callback
- Requisition-only boundary
- Missing lifecycle orchestration
Revision Information
- Status: Draft
- Last reviewed: 2026-07-20
- Review cycle: Quarterly