-
Notifications
You must be signed in to change notification settings - Fork 36
feat: ESSR protected client APIs #351
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
iFergal
wants to merge
10
commits into
WebOfTrust:main
Choose a base branch
from
cardano-foundation:feat/essrAPI
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
f7cfb9d
feat: ESSR client authentication
iFergal 0441be2
fix: expose headers for CORS
iFergal 3b080f8
fix: handle rep.text responses (needs tests)
iFergal 61e11c3
refactor: remove unnecessary strip (was from debugging) [skip ci]
iFergal 1532439
Merge remote-tracking branch 'origin/main' into feat/essrAPI
iFergal 6edad46
feat: allow both signed headers and ESSR for authentication, signify …
iFergal 1b457ca
test: coverage for serializeResponse
iFergal ec5c93a
feat: better error msgs and test coverage for signed headers
iFergal b3d6181
fix: unquote request path after verifying inbound ESSR
iFergal 1d83e66
fix: calc content-length in environ by bytes not chars and test
iFergal File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pfeairheller Passcode rotation (
PUT /agent/{caid}) in Signify doesn't use signed headers (just has a signed body), like the rest of the/agentendpoints, so perhaps this shouldn't be checking for signed headers here. If not, I can update Signify to use the correct fetch, and adjust this to accept ESSR if needed.Any idea @rodolfomiranda?