-
Notifications
You must be signed in to change notification settings - Fork 82
Open
Description
Description:
As an identity and access management system user, I want the MOSIP to support encryption and decryption using the ECC algorithm So that user credentials and sensitive data can be securely encrypted, transmitted, and decrypted to prevent unauthorised access.
Acceptance Criteria:
- ECC Encryption:
- The IDA module must allow encryption of sensitive auth data (e.g., auth request, otp, KYC data) using ECC public keys before transmitting data.
- ECC Decryption:
- The IDA module must decrypt incoming encrypted data (auth request) using the ECC algorithm
- During KYC authentication decryption process must ensure that only authorized users with valid private keys can decrypt the data.
- Authentication & Authorization:
- ECC encryption must be used during user authentication (e.g., signing or encrypting access tokens) to ensure that only legitimate users gain access to resources.
- The IDA module must verify digital signatures using ECC during authorization to validate requests and responses.
- Error Handling & Security Alerts:
- The system must provide clear error messages when ECC encryption or decryption fails, without exposing sensitive details.
- Compliance & Auditability:
- Encryption and decryption events should be logged for audit purposes, ensuring traceability and accountability in the identity and access lifecycle.
- Backward Compatibility:
- Enabling system to sign downloaded UIN with RSA, ECC, Eddsa Algorithm
- Migration Compatibility:
- Allowing the users to switch between RSA, ECC and Eddsa (Xdh - for encryption/decryption)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels