Hello MOSIP community,
We are designing a Verifiable Credentials (VC) ecosystem using the full Inji stack (Wallet, Certify, Verify).
For user authentication, we have a robust Identity Provider (IdP) already in place. This could be an in-house Keycloak instance or a national eID system that already supports its own secure biometric authentication. We have successfully integrated our Inji services directly with this IdP via standard OIDC.
Our core architectural question is: What is the specific value proposition of introducing eSignet as a middleware between our Inji services and our existing, biometric-capable IdP?
We are trying to pinpoint the key advantages over our current direct integration, especially considering our IdP is already feature-rich:
-
Federation Gateway: Is the primary benefit to abstract the direct connection, allowing us to plug in other IdPs in the future without re-engineering our relying parties?
-
Biometric Flow: Since our IdP already handles the entire secure biometric authentication flow (capture, matching, and response), what value does eSignet add to this specific transaction? Does it simply proxy the request, or does it enhance it in terms of security or auditing?
-
Enhanced Consent/Assurance: Does eSignet provide a more granular, standardized, or auditable consent and Level of Assurance (LoA) management layer than what is typically available in a national IdP or a mature platform like Keycloak?
In short, when a direct integration with a trusted, biometric-enabled IdP is working, what are the compelling reasons to add eSignet’s architectural layer?
We appreciate any insights you can share.
Thank you!