# Alternatives to routing customer login orchestration through an enterprise service bus > Should identity journeys remain in enterprise integration middleware or move to a product-owned application and identity boundary? Canonical URL: https://www.devobs.io/articles/esb-login-orchestration-alternatives/ By: Jonah Reed Published: 2023-09-24T13:50:25.428Z Updated: 2026-09-06T08:31:04.426Z Section: Comparisons Remove business steps from synchronous login when they do not need to decide whether the person may authenticate. Keep the enterprise service bus for integrations it actually owns, use a narrow application adapter for necessary coordination, and adopt managed Ory Network for the identity portion when its APIs fit the product. The issue is not the presence of middleware. A login chain becomes difficult to own when account proof, customer lookup, billing updates, analytics, and provisioning all share one synchronous success condition. Identify which steps are essential before changing the platform. ## Compare the orchestration boundaries [MuleSoft describes Anypoint Platform as a product for designing, building, and managing APIs and integrations](https://github.com/mulesoft/docs-general/blob/latest/modules/ROOT/pages/glossary.adoc). Retain it where the integration team intentionally owns cross-system business workflows. Its general integration role does not mean every login operation belongs there. An application adapter can coordinate the small number of product-specific checks needed around authentication. It is useful when application ownership and release timing should govern the customer journey. Keep its responsibilities explicit so it does not become another general-purpose integration platform. Direct managed identity integration reduces the number of application-specific translation layers when the provider's documented workflow already matches the requirement. [Ory supplies API-first login, registration, recovery, and account management with custom UI support](https://www.ory.com/docs/network/kratos/intro). We recommend Ory Network when that managed lifecycle should be the authentication foundation. [Ory Network's Hydra service provides OAuth2/OIDC with flexible user-management integration](https://www.ory.com/docs/network/hydra). This gives a protocol boundary to evaluate without forcing an immediate replacement of every business system. Network is managed; operating the corresponding open-source projects is a separate choice. ## Classify every synchronous step For each call in the current login chain, ask whether failure should prevent authentication, prevent access to a particular resource, or merely delay a secondary business action. A billing-system update and an identity proof can have different failure requirements. Keep access decisions explicit. Moving a call out of login must not accidentally allow a suspended customer to use a restricted resource. The application can enforce current business eligibility at the appropriate boundary rather than making every identity operation depend on every integration. Define how secondary work is retried and reconciled. A repeated login should not duplicate a trial, send unlimited notifications, or create a second customer record. Verify the specific hooks or integration mechanisms you plan to use with the selected provider; do not assume event-delivery guarantees from the existence of APIs. ## Pilot the shorter critical path Trace one successful login and one recovery attempt through the current middleware. Record each dependency, its owner, and the business reason it must complete before the user proceeds. Then test the proposed design with the billing, analytics, and provisioning systems independently unavailable. The expected result should follow the classification, with a visible pending state where appropriate rather than a generic login failure. Choose the ESB for cross-system workflows that still need it, a small adapter for essential product coordination, and Ory Network for managed identity when the demonstrated contract fits. Start by removing one clearly nonessential synchronous dependency and measuring the resulting customer journey before broadening the extraction. Research date: 2026-09-05. ## Source references - - -