T4: Fix gateway routing for Identity service

[devin-ai-integration]

Summary

Remove the PathRemovePrefix transform from the identity-route in src/ApiGateway/appsettings.json.

The Identity service controller uses [Route("api/[controller]")], so it expects the full /api/identity/… prefix on incoming requests. The PathRemovePrefix: "/api/identity" transform was stripping that prefix before forwarding, causing the service to receive bare paths like /login instead of /api/identity/login — resulting in 404s.

 "identity-route": {
   "ClusterId": "identity-cluster",
-  "Match": { "Path": "/api/identity/{**catch-all}" },
-  "Transforms": [{ "PathRemovePrefix": "/api/identity" }]
+  "Match": { "Path": "/api/identity/{**catch-all}" }
 }

Verified via docker compose: register, login, and 401 on /users without token all work correctly through the gateway at localhost:5000.

Link to Devin session: https://partner-workshops.devinenterprise.com/sessions/0f07b7a8f1014aec962930431c54da9f
Requested by: @mbatchelor81

---

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring

[devin-ai-integration]

Devin Review found 1 potential issue.

[devin-ai-integration]

🚩 Other service routes may have the same prefix-stripping mismatch that was fixed here for identity

The identity route's PathRemovePrefix was removed because the Identity service controller uses [Route("api/[controller]")] (IdentityController.cs:9), which means it expects the full path /api/identity/.... The same pattern applies to the other services — for example, CustomerController uses [Route("api/[controller]")] (Customer.API/Controllers/CustomerController.cs:6), resolving to api/customer (singular). But the gateway matches /api/customers/ (plural) and strips that prefix, forwarding bare paths like / or /{id} to the customer service, which expects api/customer/.... This means the customer, order, product, and notification routes likely have the same bug that was just fixed for identity — the PathRemovePrefix transforms would result in 404s unless those services use different route prefixes or the controller names happen to match the plural gateway paths. Worth verifying whether the remaining four routes need the same fix.

(Refers to lines 16-34)

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[devin-ai-integration]

Valid observation — the other service routes may indeed have similar routing mismatches (especially the plural/singular discrepancy like /api/customers/ vs api/customer). However, this PR is intentionally scoped to the identity route only per task requirements. The other routes should be evaluated and fixed in a separate PR.