You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Design the architecture for the Pending Registration Service (PRS), responsible for handling pending user registrations. The service will store registration details and OTPs, providing APIs for OTP verification and retrieval of pending registrations.
Requirements:
REST API for creating and verifying pending registrations.
Store phone numbers, public keys, and OTPs securely.
Integrate with SMS Gateway for OTP delivery.
Endpoints:
POST /prs/register: Create pending registration.
POST /prs/verify-otp: Verify OTP.
GET /prs/registration/{id}: Get registration by ID.
Acceptance Criteria:
Successful registration and OTP verification.
Secure data handling.
Estimate: 3
The text was updated successfully, but these errors were encountered:
nancymuyeh
changed the title
Create an Architecture for PRS
(TK-008)Create an Architecture for PRS
Oct 17, 2024
Description:
Design the architecture for the Pending Registration Service (PRS), responsible for handling pending user registrations. The service will store registration details and OTPs, providing APIs for OTP verification and retrieval of pending registrations.
Requirements:
REST API for creating and verifying pending registrations.
Store phone numbers, public keys, and OTPs securely.
Integrate with SMS Gateway for OTP delivery.
Endpoints:
POST /prs/register: Create pending registration.
POST /prs/verify-otp: Verify OTP.
GET /prs/registration/{id}: Get registration by ID.
Acceptance Criteria:
Successful registration and OTP verification.
Secure data handling.
Estimate: 3
The text was updated successfully, but these errors were encountered: