Set up alternative authentication for when github OAuth is 'down'
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
- elixir, github
- Domain
- authentication, backend
Research direction
Start by tracing the current GitHub OAuth flow and how user records are persisted. Define the fallback flow for detecting OAuth failure, sending a one-time email login link, and maintaining the session cookie. Done means users can access their backed-up data during GitHub outages and log out securely.
Written by the indexing model from the issue text.
Description
As a gh-backup user
I want to be able to authenticate myself without having to rely on github Oauth running
So that I have secure access to my github data even when github is having technical difficulties.
- Store user's email addresses in the db
- Recognise when github OAuth is not working and give user option to authenticate by email
- Send user an email with a login link, when user clicks on the link they are logged in
- Store a cookie so that the user is authenticated until they log out
Original Question:
Do we have to use github auth to authorise access to backed up data?
If yes, how do we allow people to access their data when github is down if we can't authenticate them?
If github is down will their authorisation mechanism also be?
Answer:
When someone authenticates when github is up as usual then we will record their email address. Then on an occasion when github is offline we will allow them authenticate using our record of their email. We will send them a one time login link to their email. We will also add a cookie to keep them logged in until they log out.
- Dominant language
- Elixir
- Stars
- 33
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 dwyl/github-backup
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 15/100
dwyl/github-backup#138 ·
-
discuss enhancement priority-2
dwyl/github-backup#136 · 10 comments · 1 assignee ·
-
😕 Openhelp wanted priority-2
Difficulty 5/5 Over a week Newbie friendliness 25/100
dwyl/github-backup#135 · 1 comment · 3 reactions ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 20/100
dwyl/github-backup#133 ·
-
discuss priority-4 technical
Difficulty 5/5 Over a week Newbie friendliness 20/100
dwyl/github-backup#132 · 3 comments · 1 reaction ·
All issues in dwyl/github-backup
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
phoenixframework/phoenix#6847 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
beyond-all-reason/teiserver#1584 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ash-project/ash#2954 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
membraneframework/boombox#149 ·