Files
2ticketss/01-gh-issue-generator/SAMPLE_ISSUE.md
bennettldavid f74bab9ed4 # 2ticketss
2 complementary command-line tools for GitHub issue management
- **00-jira-to-gh-issues**: A Rust tool that converts Jira CSV exports to GitHub issue markdown files compatible with gh-issue-generator. It handles messy CSV data and preserves issue metadata
- **01-gh-issue-generator**: A Rust tool that creates GitHub issues from Markdown files with YAML front matter. It parses structured Markdown, supports batch processing, and integrates with GitHub CLI
2025-04-04 22:32:49 -06:00

67 lines
1.7 KiB
Markdown

---
title: Implement user authentication service
status: ready
labels:
- feature
- security
- backend
assignees:
- developer1
- developer2
milestone: v1.0
project: Development Roadmap
parent: 42
---
# User Authentication Service Implementation
## Overview
We need to implement a comprehensive user authentication service that handles registration, login, password reset, and account management.
## Requirements
- Secure password handling with bcrypt
- JWT token generation and validation
- Email verification flow
- Two-factor authentication support
- Rate limiting for login attempts
- Session management
## Tasks
- [ ] Design authentication database schema
- [ ] Implement user registration endpoint
- [ ] Add email verification flow
- [ ] Create login endpoint with JWT token generation
- [ ] Implement password reset functionality
- [ ] Add two-factor authentication
- [ ] Set up rate limiting for login attempts
- [ ] Implement session management
- [ ] Write unit and integration tests
- [ ] Create API documentation
## Technical Notes
```
POST /api/auth/register
{
"email": "user@example.com",
"password": "securePassword",
"name": "User Name"
}
```
Authentication should follow OAuth 2.0 standards where applicable.
## Related Resources
- [JWT Best Practices](https://auth0.com/blog/a-look-at-the-latest-draft-for-jwt-bcp/)
- [OWASP Authentication Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/Authentication_Cheat_Sheet.html)
## Acceptance Criteria
1. All authentication endpoints pass security review
2. Password storage follows current best practices
3. Login and registration flows have appropriate rate limiting
4. All user flows are documented in the API docs