RealDevSquad / RealDevSquad/website-backend
Enabling 2FA for Email Notifications in RDS and environment variables to the staging and prod environment
Open
@prakashchoudhary07 is already working on this.
Since Oct 13, 2024.
- Dominant language
- JavaScript
- Stars
- 74
- Forks
- 276
- Avg merge
- 1d 26m
- Merged PRs (30d)
- 14
Description
Issue Description
The issue is about enabling Two-Factor Authentication (2FA) for sending email notifications in the RDS system and generating a standardized message format for emails. The main purpose is to secure email notifications and ensure all messages follow a consistent format.
Expected Behavior
- Email notifications should be sent securely using 2FA.
- Message formats should be consistent across all notifications.
- Collaboration with Ankush and Prakash to add the email, app password, host, port in the staging and prod environment.
Current Behavior
- No such thing exists
- The message format is not standardized and needs to be generated, as we just need to send the hello message.
Steps to generate app password
Firstly, please create a dummy email address for staging. then follow these steps
- Enable 2FA Link to enable this
- Create an app password on clicking this link
- Login to the email
- Generate the app password
- Store the password generated
- And finally paste all these to the staging and prod environment
- this the details we need to add.
email: "RDS_EMAIL",
password: "RDS_EMAIL_PASSWORD",
host: "SMTP_HOST",
port: {
__name: "SMTP_PORT",
__format: "number",
},
},
Environment variable names
- RDS_EMAIL : will the email id
- RDS_EMAIL_PASSWORD : will be the password generated by following steps motioned above.
- SMTP_HOST : as we are using nodemailer we would need a stmp host to make it work. If you are using gmail feel free to add
smtp.gmail.com - SMTP_PORT: a port number, typically
587
Reproducibility
- This issue is reproducible
- This issue is not reproducible
Severity/Priority
- Critical
- High
- Medium
- Low
Checklist
- I have read and followed the project's code of conduct.
- I have searched for similar issues before creating this one.
- I have provided all the necessary information to understand and reproduce the issue.
- I am willing to contribute to the resolution of this issue.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.