Sign-in Page Functionality and Actions
Overview
What happens when you sign-in using different authentication methods?
Architecture review date: 1. Aug 2024
Project lead: @Ian Jones (Unlicensed)
What Happens, Actions and Consequences
| Action | Consequence | Priority | Notes |
|---|---|---|---|
| Username/email authentication, without 'Remember me' being ticked | A session cookie is set, with a 10 day limit | ||
| Username/email authentication with 'Remember me' being ticked | A cookie is set to authenticate for 30 days | ||
| Username/email authentication, with or without 'Remember me' being ticked, followed by TFA, without 'Remember this device for 30 days' being ticked on the TFA page | A session cookie is set with a 10 day limit | ||
| Username/email authentication, with or without 'Remember me' being ticked, followed by TFA, with 'Remember this device for 30 days' being ticked on the TFA page | A session cookie is set with a 10 day limit, but TFA is not required for 30 days | ||
| SSO authentication | A session cookie is set, with a 10 day limit |
Stakeholders
| Role | Name | Definition | Key Success Metrics |
|---|---|---|---|
| CTO | @Jody Van Vestraut | ||
| CPO |
Goals
Software Quality Attributes
e.g., Availability, Efficiency, Extensibility, Functionality, Integrity, Interoperability, Maintainability, Modifiability, Performance, Portability, Reliability, Scalability, Security, Usability, Other
| Attribute | Definition | Key Success Metrics | Notes |
|---|---|---|---|
Next Steps
| Project | Description | Estimate | Documentation | Target Release Date |
|---|---|---|---|---|
| 1 | ||||
| 2 |