-
Notifications
You must be signed in to change notification settings - Fork 98
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
ES-1856 updated Readme file as per review comments (#1023)
* ES-1856 Signed-off-by: ase-101 <[email protected]> * ES-1856 Signed-off-by: ase-101 <[email protected]> * ES-1856 Signed-off-by: ase-101 <[email protected]> * Updated branch name Signed-off-by: ase-101 <[email protected]> --------- Signed-off-by: ase-101 <[email protected]>
- Loading branch information
Showing
14 changed files
with
85 additions
and
30 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
# Overview | ||
|
||
eSignet offers a seamless and straightforward solution for incorporating an existing trusted identity database into the | ||
digital realm via plugins. | ||
|
||
## Design Objectives | ||
|
||
1. Should be an overlay solution on top of any of the existing identity API. Users can adopt the IDP solution and plugin the backend identity verification against their existing identity registry. | ||
2. Should be able to independently operate without much dependency on existing services of MOSIP | ||
3. Support all the mandatory features of OIDC (Open ID Connect) specification so the solution can be OIDC certified | ||
4. When there are multiple options for a OIDC feature, support only the most secure option. | ||
5. All integration libraries to ID system should be a runtime plugable to reuse the official container images which helps with easier upgrades. | ||
6. Number of containers / runable applications to be kept to a minimum to avoid management overhead. | ||
7. Standard interfaces to be used as much as possible for integrations between components | ||
8. Should manage all the transactional data in expiring cache to increase data retrieval performance | ||
9. The API endpoint exposed should be stateless (avoid stickiness) to support better horizontal scaling. | ||
10. IAM based API authorization should have configuration to switched off to allow external network based mechanisms to control authorization and avoid high dependency on IAM system | ||
11. All personally identifiable information (PII) should be kept encrypted in storage and transit | ||
|
||
## Authorization code flow | ||
|
||
![eSignet-design-OIDC-authorize-flow.png](../eSignet-design-OIDC-authorize-flow.png) | ||
|
||
## Authorization code flow using biometric authentication | ||
|
||
![esignet-with-bio-auth.png](../esignet-with-bio-auth.png) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
# Overview | ||
|
||
eSignet offers QR code based login using Wallet apps. Wallet apps store verifiable credentials(VC). Both demographic and biometric data | ||
are available in the VC. Biometric data in the VC could be leveraged to perform local 1:1 biometric match to authenticate into eSignet and access any relying party services. | ||
|
||
## Binding Process | ||
|
||
VC issued by an identity system against an individual ID. Issued VC should be mapped to a key pair, private key resides in the wallet app's secure storage. | ||
The corresponding public key is mapped to the same individual ID in the identity system (VC issuer). | ||
|
||
![esignet-wallet-binding.png](../esignet-wallet-binding.png) | ||
|
||
## Wallet based authentication using QR code | ||
|
||
Below diagram depicts the QR code based authorization code flow in eSignet. | ||
|
||
![esignet-authorize-qr-code-flow.png](../esignet-authorize-qr-code-flow.png) | ||
|
||
|
||
|
This file was deleted.
Oops, something went wrong.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
File renamed without changes
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters