Bearer token authentication for the frontend API
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- javascript
- Domain
- api, authentication, security
Research direction
Start by tracing the existing Basic authentication path for API access and its LDAP credential handling. Define the Bearer-token flow around MFA, token scopes and lifetimes, and audit logging; done should mean API users can authenticate with MFA and use appropriately limited tokens instead of Basic credentials.
Written by the indexing model from the issue text.
Description
We currently support Basic authentication via LDAP credentials for API access.
We want to move to Bearer authentication instead, where users can authenticate with MFA and get a token to use in automations. This has many advantages:
- the blast radius of a lost ASF password is reduced (the password doesn't give access to the API without MFA)
- the risk of a lost ASF password is reduced (if the dash API is ever compromised, it would no longer allow the attacker to steal ASF passwords)
- the impact of a compromise of a tool that uses this API is reduced (since it can no longer expose an ASF password, and tokens can have limited scopes and lifetimes)
- we can have better audit logging of different types of authentication
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 6
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 8
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 apache/security-dash
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
apache/security-dash#3 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
apache/security-dash#29 ·
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 45/100
apache/security-dash#26 ·
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 55/100
apache/security-dash#25 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 62/100
apache/security-dash#24 ·
All issues in apache/security-dash
Similar issues
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
githubnext/gh-aw-workshop#3692 ·
-
agent/guide documentation hive/hosted-available-lke648397-260827-5n31
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Add: BuyPass TV Openchannels:add check:passed
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
S: triage
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100