# Http://localhost:3000/v1/esignet/authorization/v3/oauth-details is failed with invalid\_redirect\_uri

**URL:** <https://community.mosip.io/t/http-localhost-3000-v1-esignet-authorization-v3-oauth-details-is-failed-with-invalid-redirect-uri/2503>\
**Category:** General\
**Created:** [January 19, 2026, 8:38am UTC](https://community.mosip.io/t/http-localhost-3000-v1-esignet-authorization-v3-oauth-details-is-failed-with-invalid-redirect-uri/2503 "2026-01-19T08:38:43Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![joni](https://avatars.discourse-cdn.com/v4/letter/j/3d9bf3/32.png) [@joni](https://community.mosip.io/u/joni)\
**Post date:** [January 19, 2026, 8:38am UTC](https://community.mosip.io/t/http-localhost-3000-v1-esignet-authorization-v3-oauth-details-is-failed-with-invalid-redirect-uri/2503/1 "2026-01-19T08:38:43Z")

</div>

Dear Tim Mosip,

I am already running the esignet with docker compose.

Here is the step that already done :

1. Create OIDC client with postman
2. Running mock-relying-party-ui with client that already created in step 1
3. Running mock-replying-party-service with private key from postman in step 1

Now the button login already show , but when i clicked sign in with esignet always fail with error when hit [http://192.168.100.49:3000/v1/esignet/authorization/v3/oauth-details](http://192.168.100.49:3000/v1/esignet/authorization/v3/oauth-details) from url [http://192.168.100.49:3000/authorize?client\_id=IIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAgvURe&request\_uri=urn%3Aietf%3Aparams%3Aoauth%3Arequest\_uri%3ACEro3SBVVpmS5btcRBknyQJCueqQztrVjsZcYep8c60&ui\_locales=en](http://192.168.100.49:3000/authorize?client_id=IIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAgvURe&request_uri=urn%3Aietf%3Aparams%3Aoauth%3Arequest_uri%3ACEro3SBVVpmS5btcRBknyQJCueqQztrVjsZcYep8c60&ui_locales=en)

Here is the request to oauth-details sent from oidc-ui

```auto
{"clientId":"IIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAgvURe","scope":null,"responseType":null,"redirectUri":null,"display":null,"prompt":null,"nonce":null,"state":null,"acrValues":null,"maxAge":null,"claims":null,"claimsLocales":null,"uiLocales":"en","dpopJkt":null,"codeChallenge":null,"codeChallengeMethod":null,"idTokenHint":null}","logger_name":"io.mosip.esignet.services.AuthorizationServiceImpl","thread_name":"http-nio-8088-exec-6","level":"INFO","level_value":20000,"appName":"esignet","traceId":"7033e79c63c50e87","spanId":"7033e79c63c50e87","spanExportable":"true","X-Span-Export":"true","X-B3-SpanId":"7033e79c63c50e87","X-B3-TraceId":"7033e79c63c50e87"}

```

In the container log i just add some debug in esignet -service code that the request\_uri is null ,it seems the oicd-ui did not forward the request from the relying server ?

Please advice

 ![UILogin](https://europe1.discourse-cdn.com/flex017/uploads/mosip1/original/2X/2/25f6e21970162710878a26899f1815fd4dd90e0f.jpeg)

---

<div class="post-metadata">

**Author:** ![Prathmesh\_Jadhav](https://dub1.discourse-cdn.com/flex017/user_avatar/community.mosip.io/prathmesh_jadhav/32/1628_2.png) [@Prathmesh\_Jadhav](https://community.mosip.io/u/Prathmesh_Jadhav)\
**Post date:** [January 20, 2026, 4:14am UTC](https://community.mosip.io/t/http-localhost-3000-v1-esignet-authorization-v3-oauth-details-is-failed-with-invalid-redirect-uri/2503/2 "2026-01-20T04:14:53Z")

</div>

Hi **[joni](https://community.mosip.io/u/joni)**!

Thanks for reaching out.  
We are looking into your query and will get back to you soon!  
Until then, happy coding with MOSIP!

Best regards,  
Prathmesh Jadhav  
Team MOSIP

---

<div class="post-metadata">

**Author:** ![joni](https://avatars.discourse-cdn.com/v4/letter/j/3d9bf3/32.png) [@joni](https://community.mosip.io/u/joni)\
**Post date:** [January 21, 2026, 4:02am UTC](https://community.mosip.io/t/http-localhost-3000-v1-esignet-authorization-v3-oauth-details-is-failed-with-invalid-redirect-uri/2503/3 "2026-01-21T04:02:18Z")

</div>

Hi Team Mosip,

Additional findout , after i change the sign on button plugin url to : [https://esignet.dev.mosip.net/plugins/sign-in-button-plugin.js](https://esignet.dev.mosip.net/plugins/sign-in-button-plugin.js) instead of using button plugin url from docker compose esignet branch 1.7 , the login page now is shown.

I think the problem is in the button plugin js .

---

<div class="post-metadata">

**Author:** ![zesu2210](https://avatars.discourse-cdn.com/v4/letter/z/ad7895/32.png) [@zesu2210](https://community.mosip.io/u/zesu2210)\
**Post date:** [January 21, 2026, 4:34pm UTC](https://community.mosip.io/t/http-localhost-3000-v1-esignet-authorization-v3-oauth-details-is-failed-with-invalid-redirect-uri/2503/4 "2026-01-21T16:34:14Z")

</div>

Hi @joni ,

Could you please confirm the following:

- **Branch or tag** you are using to run the `docker-compose` file for **eSignet** and its related services.

- **How** you are running the **mock-relying-party-ui** and its services.

For the mock-rp-ui:

- **If you are running it using Docker Compose** , please use this file:  
[esignet-mock-services/docker-compose/mock-relying-party-portal-docker-compose.yml at v0.12.0 · mosip/esignet-mock-services · GitHub](https://github.com/mosip/esignet-mock-services/blob/v0.12.0/docker-compose/mock-relying-party-portal-docker-compose.yml)

- **If you are running it manually** , ensure the same properties defined in the Docker Compose setup are added to this environment configuration file:  
[esignet-mock-services/mock-relying-party-ui/public/env-config.js at v0.12.0 · mosip/esignet-mock-services · GitHub](https://github.com/mosip/esignet-mock-services/blob/v0.12.0/mock-relying-party-ui/public/env-config.js)

If you have any questions, please feel free to ask.

Thanks & Regards  
Zeeshan

---

<div class="post-metadata">

**Author:** ![system](https://europe1.discourse-cdn.com/flex017/uploads/mosip1/original/1X/f60a343830fe848c9a68e2d1cc654d0cb7fbbaf2.svg) [@system](https://community.mosip.io/u/system)\
**Post date:** [January 31, 2026, 4:35pm UTC](https://community.mosip.io/t/http-localhost-3000-v1-esignet-authorization-v3-oauth-details-is-failed-with-invalid-redirect-uri/2503/5 "2026-01-31T16:35:01Z")

</div>

Closed on January 31, 2026, 4:35pm UTC

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.
