Entryway update handle flow, pds and agent caching #1785
Merged
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.
A few misc fixes, improvements, and tweaks to the entryway setup:
getAccountByEmail()
which was giving anull
for the user's did.getPds(did)
results which is in the hot path of proxying.AtpAgent
s for the entryway's pdses.admin.updateAccountHandle
endpoint to avoid entryway and pdsidentity.updateHandle
routes depending on each other.didDoc
alongside credentials when the pds endpoint is one of the entryway's pdses.