client certificate authorization, mTLS, and simplification of architecture #9
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
TL;DR: Client certificate authentication is the most important change, but I started from scratch for simplicity. I did it because it took me a long time to figure out what TAP was actually doing, and then saw that the central registry concept would require handling a duplicate request for some large portion of the entire internet, and doing a terra-scale lookup for each, so I made an alternative architecture for much better scalability. Maybe something to pick at.
Proposed Changes
1. Unified Stack
src/with dedicated modules foragent,proxy,registry,authority, andmerchant.2. Enhanced Protocol & Security
3. Lightweight Frontend
Architecture Comparison
I hope this reference implementation provides some useful ideas for the project's evolution.