Document trade-offs between DPoP and MTLS
Open
Nobody has claimed this yet.
component: Implementation & Deployment Advice
migrated-from-bitbucket
priority: minor
type: task
- Dominant language
- HTML
- Stars
- 3
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Originally submitted by dgtonge (Dave Tonge) on 2022-08-10
In relation to https://bitbucket.org/openid/fapi/pull-requests/365 we discussed that it might be helpful to document some of the trade offs between DPoP and MTLS
Bitbucket status: open
Bitbucket origin: issue 537
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.
Research direction
Start by reading the discussion connected to Bitbucket pull request 365 and compare the DPoP and MTLS approaches in the FAPI context. Document the relevant trade-offs clearly, with the completed comparison serving as the definition of done.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, documentation, security
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100