Hi MOSIP team,
I’m an independent developer studying MOSIP and would like access to the Collab sandbox to learn the platform and run a small proof-of-concept.
My details:
What I’d like to do:
- Explore the Collab environment and understand the identity issuance and authentication flows end to end.
- Run a MOSIP service locally (Java/Spring Boot, Docker Postgres) and integrate it with Collab.
- Learn how the UI actions map to backend APIs.
Access requested:
- Collab environment access
- A demo UIN / test credentials for sample identity data
- Authentication Partner (Partner Portal) access to create and test an eSignet / OIDC client
As I learn, I may explore other partner areas later and am happy to request those separately if a specific need arises. I’ll gladly complete any verification steps (public keys, machine details) required.
Thank you!
Hi @Soundarya
Thank you for reaching out with your query.
Regarding the access required to explore the MOSIP Collab environment, you can refer to the Collab Getting Started Guide for details on how to get access and get started.
Meanwhile, if you need a UIN for testing, you can use the UINs that are already available in the Collab environment : https://self-register.collab.mosip.net/
Regards,
Varaniya S
Team MOSIP
1)After logging in with the mock ID via eSignet, the session expires immediately and redirects me back to the login/email page. Tried Brave and incognito with shields down — same result, UIN 2345890124, OTP 111111
2)I registered on the Collab self-registration portal and received the confirmation email, but it did not include the UIN PDF/card, and I’m not receiving the OTP when trying to log in. Could you please help? Thanks
Any update on this?
I need access to sandbox ,could anyone help on this?
Hello MOSIP team,
I’m seeing the same issues. A browser trace shows send-otp, authenticate, and claim-details all return 200 and an authorization code is issued. The failure occurs at /mock-relying-party-service/fetchUserInfo (500); its Axios error points to the eSignet /oauth/v2/token call also returning 500. The private_key_jwt audience, issuer, subject, and expiry appear valid, so please check the RP client key registration or deployment configuration. My newly issued UIN is also rejected as invalid before OTP.
Hi @Yuta_Hoshina / @Soundarya ,
The internal team has investigated and resolved the issue. Please try again, and you should receive the UIN card via email as well.
Regards,
Varaniya S
Team MOSIP
Hi @Varaniya1
Thank you for checking. My UIN was successfully issued, and I also received the PDF as an email attachment.
However, the following issues remain unresolved:
Testing with the Mock ID:
After entering the OTP, the healthcare page appears briefly, but it immediately displays “Session Expired.”
Logging in with my newly issued UIN:
After entering the UIN and clicking “Get OTP,” I receive the error “Please Enter Valid Individual ID.”
Could these be separate integration issues between the Mock Relying Party and eSignet, and between UIN issuance and the eSignet authentication backend?
Thank you.
Yuta
Hi @Yuta_Hoshina & @Soundarya ,
We have these logged as known issues and team is working on both. Will update you once these are fixed.
Thanks for your understanding,
Regards,
Rachik Raj Sharma
Team MOSIP
Hi @Rachik_Raj_Sharma & @Varaniya1 ,
Thankyou for checking,
Is there a JIRA project or GitHub board or setup document where local-setup and environment issues are tracked, and can we get access to it?
Do we need permissions/access (Keycloak, DB, etc.) for local?
Can it be made to work completely locally?
which are the modules that can be setup completely in local?
Hi @Yuta_Hoshina @Soundarya ,
Thanks for your patience, the above issues are now resolved.Please, check from your end. Please feel free to reach out to me for any other queries.
Also, @Soundarya we are working on making a community accessible board where all the tickets will be visible.
For local set up of eSignet you can refer here.
Regards
Rachik Sharma
Team MOSIP