[BUG] eSignet UI login fails with "Failed to get requestUri" (500) for client using regex redirect_uri pattern

[prathmeshj12]

Description

Relying-party login via eSignet fails in the browser UI with the toast "Failed to get Request URI. Please try again later." immediately after clicking "Sign In with eSignet", even though the same OIDC client completes a full end-to-end login successfully when driven directly through the API (Postman). Root cause traces to a 500 Internal Server Error on the relying-party's request-URI creation call.

Steps to Reproduce

Precondition:

1. Create client with redirect uri in regex format - https://healthservices-go.esqa.mosip.net/userprofile/*

Steps to Reproduce

1. Navigate to https://healthservices-go.esqa.mosip.net (Health Portal sign-in page).
2. Click "Sign In with eSignet".
3. Observe the page immediately redirects to: https://healthservices-go.esqa.mosip.net/userprofile?error_description=Failed+to+get+Request+URI.+Please+try+again+later.&error=request_uri_error
4. A toast is shown: "Failed to get Request URI. Please try again later."
5. Open DevTools → Network tab and repeat steps 2–4 to capture the failing call (see Evidence below).

Actual Result:
Relying-party login via eSignet fails in the browser UI with the toast "Failed to get Request URI. Please try again later." immediately after clicking "Sign In with eSignet"

Expected Behavior

Clicking "Sign In with eSignet" should push the authorization request, receive a valid request_uri, and redirect the browser to eSignet's /authorize screen so the user can proceed with authentication — matching the successful flow already verified via Postman for the same client.

Screen.Recording.2026-09-11.at.5.34.02.PM.mov

Attachment / Evidence / Docs / Screenshots

No response

Root Cause

No response

Additional Context

No response