Http://localhost:3000/v1/esignet/authorization/v3/oauth-details is failed with invalid_redirect_uri

1

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 from url 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

{"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
UILogin1920×971 117 KB

2

Hi 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

3

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 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 .

4

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 have any questions, please feel free to ask.

Thanks & Regards
Zeeshan

5

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