#Authentication OAuth support for logging into Runbox
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- angular, typescript
- Domain
- authentication, full-stack
Research direction
Start by reading the login page and the existing authentication flow in the Runbox 7 web app. The issue describes redirecting to an authorization server, handling a one-time code and exchanging it for tokens, but names no files, tests, or entry points. Done means users can sign in through the described flow, including 2FA when enabled.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
OAuth is a common authorization scheme that is increasingly popular, and would make logging into Runbox simpler, more secure, and more integrated with other services.
Describe the solution you'd like
Suggested user workflow:
- Initiation: The user visits the Runbox login page and clicks the "Login" button.
- Redirection: The browser is automatically redirected from the web mail interface to the Runbox auth server.
- Authentication: The user enters their Runbox credentials (username and password) and performs Two-Factor Authentication (2FA) if enabled.
- Consent (Optional): If it is the user's first time logging in through this method, they might see a screen asking them to confirm that the Runbox Web App can access your profile and email data.
- Token Exchange: Behind the scenes, the authorization server sends a one-time code back to the web interface, which exchanges it for an ID Token and an Access Token.
- Access Granted: The browser redirects the user back to your inbox. The user is logged in with a secure session based on the tokens provided, without the web app ever needing to store the actual password in its session memory.
- Dominant language
- TypeScript
- Stars
- 132
- Forks
- 55
- Avg merge
- 6d 17h
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from runbox/runbox7
-
Names in Sent folderOpen
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Keep messages selected after an operation so a second operation can be performed on the same set.Possibly taken @gtandersen claimed this 10 days ago. Openenhancement
-
#2FA App passwords copy featurePossibly taken @hoanle0126 claimed this 22 days ago. Openenhancement P3-medium
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
-
#Mail Initial index sync prompt hides message action iconsPossibly taken @LubuSeb claimed this 25 days ago. Openbug P1-urgent
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
steelbrain/node-ssh#487 ·
-
cli: `execCargoMetadata` decodes stdout per chunk, corrupting non-ASCII paths across pipe boundariesOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 62/100
lingdojo/kana-dojo#34127 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
osmlab/name-suggestion-index#13104 ·
Maintainers usually reply within 1 day