Esignet blocking issue: 403 error after login with VNID with otp

Hello esignet team,

We are integrating our relying party application with esignet and are blocked at the consent page.

Issue:

1.RP Authorization flow starts correctly from our backend.

2.User authenticated successfully with MOSIP sandbox identity using OTP.

3.Browser reaches esignet consent URL.

4.Consent UI doesn’t not render.

5.Browser network tab shows repeated fetch/XHR request named health returning 403.

6.Response body is Access Denied

7.Because consent page does not render ,we cannot approve consent and no Authorization code is returned to our callback.

8.Our Relying Party Redirect URI:

http://localhost:5000/api/auth/esignet/callback

9.chrome also tried fresh session and cleared site data

Please resolve my issue

I attached my screenshots.

Please check those and resolve my issue as soon as possible.

How much time it will take to resolve my issue?

Can anyone respond?

Why consent page is not rendered?

Hi Dileep_Munji

Thank you for reaching out to us, and sorry for the delay. Our eSignet team will get back to you soon.

Regards,
Mrudula
on behalf of Team MOSIP

Please resolve my as much as possible.

Waiting for your response.

Hi @Dileep_Munji ,

Can you share the client_id and user_id you are testing with, so that we can reproduce the issue to debug.

thanks & regards,

Hi eSignet Team,

Please find the client ID and other details below which I have received earlier,

  1. Client ID: 6RCn9jk1XbPN_DE1-A0gq5OArWJzqRScSvoNC2pvnqg

  2. Well-Known Endpoint: https://esignet-mosipid.collab.mosip.net/.well-known/openid-configuration

  3. Self-Registration Portal (MOSIP ID (National ID) Generation): https://self-register.collab.mosip.net/

  4. List of Supported Claims:
    [“birthdate”, “address”, “gender”, “name”, “phone_number”, “picture”, “email” ]

  5. Supported ACR Values for the Client:
    [“mosip:idp:acr:linked-wallet”, “mosip:idp:acr:biometrics”, “mosip:idp:acr:generated-code”]

  6. OTP: Register with a valid, accessible email address, during self regitration the OTP will be sent to that email or If you did not add a valid email during registration, you can still get an OTP! Go to smtp.collab.mosip.net (public mailbox) to get the OTP.

@Dileep_Munji - I was able to login and provide consent with below authorize URL

https://esignet-mosipid.collab.mosip.net/authorize?client_id=6RCn9jk1XbPN_DE1-A0gq5OArWJzqRScSvoNC2pvnqg&redirect_uri=http://localhost:5000/api/auth/esignet/callback&prompt=consent&response_type=code&scope=openid%20profile&state=test-state&code_challenge=wxmTR5SueS1wRSqFa5LMXJ7BgjZ-dubItVtJjblSVKg&code_challenge_method=S256

I used one of the UIN from the below page:

Please cross check once again.

But consent is not rendered for me.
Please show me is it working for that mock data by sending screenshots because I don’t have access to those mock data phone number enter otp.

How can I get OTP for mock Id?

Hi @Dileep_Munji

We use static OTP for mock which is - ‘111111’.
You can try with this and check.

Regards
Rachik Sharma
Team MOSIP

Hi @Rachik_Raj_Sharma 111111 otp is not working for mock data

Hi @Dileep_Munji ,

Can you please clarify, have you created a new UIN using the self registration portal and you are trying to use that to login? If Yes then the static OTP will not work. You can follow below:

  1. If you registered with a valid, accessible email address, the OTP will be sent to that email. Please ensure you use a valid, accessible email ID during self-registration to receive it directly.
  2. If you did not add a valid email during registration, you can still get an OTP! Go to smtp.collab.mosip.net (public mailbox) to get the OTP. (Important: You must refresh/reload the public mailbox (smtp.collab.mosip.net) to clear any previous OTPs and then click Get OTP and use the newly received one to complete login.

Regards,
Team MOSIP