fix: passing did document in options #377
Open
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.
This pull request introduces support for passing and handling the sender's DID Document throughout the authentication flow in the
auth.tshandler. The changes ensure that the sender's DID Document can be provided as an option, propagated through relevant types and methods, and included in the authentication response body.Enhancements to DID Document handling:
DIDDocumentto the imports from../typesinauth.tsto enable usage of the type throughout the file.AuthReqOptionsandAuthHandlerOptionstypes to include an optionalsenderDIDDocumentproperty, allowing the sender's DID Document to be passed into authentication operations. [1] [2]AuthHandlerclass to include thesenderDIDDocumentin the authentication response body under thedid_docfield, ensuring it is returned as part of the response.handleAuthRequestto propagate thesenderDIDDocumentoption, ensuring it is available during request handling.