fix(login): http 2 memory leak's (#11830)

# Which Problems Are Solved
All http 2 based connect-es clients caused memory leaks in our testing
using the login v2 application as the host.

# How the Problems Are Solved
Switch to connect-rpc based http 1.1 transport for the login v2

# Additional Changes
Improved the otel interceptor implementation and tests.

# Additional Context
- connect-rpc is only enabled for v2 API's so we have to make sure to
not use any v1 apis in the login but this should be the case anyways.
- Discussion #10562

---------

Co-authored-by: Max Peintner <[email protected]>
This commit is contained in:
Ramon
2026-03-17 14:29:21 +00:00
committed by GitHub
co-authored by Max Peintner
parent c1be72765c
commit fca2589fc3
11 changed files with 1294 additions and 845 deletions
-1
View File
@@ -529,7 +529,6 @@ export async function sendLoginname(command: SendLoginnameCommand) {
// user not found, check if IDPs are available when local auth is not allowed
if (!effectiveLoginSettings?.allowLocalAuthentication) {
console.log("redirecting to IDP (register allowed, password not allowed)");
logger.debug("redirecting to IDP (register allowed, password not allowed)");
const resp = await redirectUserToIDP(undefined, discoveredOrganization);
if (resp) {