Of course XAdES-BES is not supported as this offers no long-term
validity and is thus completely useless.
While constructing the XAdES-X-L, the eID DSS will only extend the
XAdES-BES to a T,C,X,X-L if the PKCS#1 signature was OK and if the
signatory is trusted (checked via the eID Trust Service). So this check
is inherent part of the construction of the XAdES-X-L by the eID DSS.
Kind Regards,
Frank.
The eID DSS does not expose Java API's. The eID DSS exposes DSS
protocols and should be used as a service.
In the future the eID DSS validation web service will be extended with
functionality to upgrade signatures. But this will only cover XAdES-X-L
to XAdES-A (and XAdES-A to XAdES-A).
Kind Regards,
Frank.
You don't have to upgrade to XAdES-X-L yourself. The eID DSS delivers
XAdES-X-L right from the start.
The focus of eID DSS is to be able to create electronic signatures
within a browser.
Kind Regards,
Frank.