Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(TK-008)Create an Architecture for PRS e3 #3

Open
Elwizzy12 opened this issue Oct 16, 2024 · 0 comments · May be fixed by #16
Open

(TK-008)Create an Architecture for PRS e3 #3

Elwizzy12 opened this issue Oct 16, 2024 · 0 comments · May be fixed by #16
Assignees
Labels

Comments

@Elwizzy12
Copy link
Contributor

Elwizzy12 commented Oct 16, 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

@nancymuyeh nancymuyeh changed the title Create an Architecture for PRS (TK-008)Create an Architecture for PRS Oct 17, 2024
@Koufan-De-King Koufan-De-King changed the title (TK-008)Create an Architecture for PRS (TK-008)Create an Architecture for PRS e3 Dec 20, 2024
@Koufan-De-King Koufan-De-King self-assigned this Jan 7, 2025
@Elwizzy12 Elwizzy12 transferred this issue from ADORSYS-GIS/webank-OnlineBanking Jan 7, 2025
@Koufan-De-King Koufan-De-King linked a pull request Jan 9, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants