Skip to content
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

[SANTUARIO-615] Implementation pre-post processing extension with xades (basic) example. #299

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

jrihtarsic
Copy link
Contributor

@jrihtarsic jrihtarsic commented Mar 24, 2024

The purpose of this PR is to present the proposals [SANTUARIO-615] for the pre/post processor for the signatures.
The use case is the request for XAdES support as requested in SANTUARIO-402 and SANTUARIO-416. The use-case already supports (Basic Signatures profile) and (with the right certificate) it pass the validation by EC DSS tool:
https://ec.europa.eu/digital-building-blocks/DSS/webapp-demo/validation

Please note that for "composing" the "XAdES" data, the generated jaxb objects are used from the xades scheme v1.4.1 and v1.3.2.

This is a experimental PR to discuss/verify the following architectural approaches for the XAdES:

  • the pre-post processing design pattern for signing (Is the approach accepted, in example is used one interface, or it wold be better to have each own for pre and post processing,.. )
  • use of jaxb generated objects with jakarta.xml.bind.(Marshaller|Unmarshaller).Currently xmlsec is using internal jaxb implementation using ElementProxy for some parts and for others DOMStructure/XMLStructure both with with internal/own/(non generated) "jaxb" object.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant