ASP.NET financial reconciliation: separate routing, HTTP methods and authorization
Routing to the correct action does not grant permission to execute it. Financial reconciliation needs explicit boundaries between reading, approving and changing records.
A matched URL is not permission
In a reconciliation application, /reconciliation/{id} may show a record while /reconciliation/{id}/approve changes its state. Routing selects the handler; it does not decide whether a user is allowed to approve a particular record. The server must check the caller, role, record ownership and current workflow state. Hiding a button in the interface does not secure the action.
HTTP methods and retries
Use GET for reading and an appropriate state-changing method, often POST, for approvals. A repeated approval must not create duplicate ledger entries: enforce workflow transitions and uniqueness on the server. Check the current state, commit the change atomically, and record the responsible actor and timestamp in an audit trail. These properties matter more than the chosen route template.
Positive, negative and boundary tests
An authorized accountant should approve an eligible record, while a user from another branch must fail even if they manually type the same URL. Two simultaneous approvals should cause one valid transition, not two accounting effects. Test the application's conflict response, anti-CSRF measures where relevant, verified identity and safe return URLs. Treat the database as the final source of truth.
2017 context versus newer frameworks
This newly written article revisits ASP.NET engineering problems relevant to 2017. Do not project modern endpoint-routing APIs onto every framework version from that period. Route registration differs across MVC and ASP.NET Core releases, while authorization and workflow validation remain essential. Check the target application's framework documentation before adopting newer examples.
Comments
No comments yet. Be the first to contribute.
✎ Write a comment