The XAdES spec defines two mechanisms for managing counter signatures:
- Use the
Type
attribute on arbitrary signatures - Use the
CounterSignature
property which contains a counter signature that actually is an enveloped signature (contained in the original one).
XAdES4j uses the second approach, hence not including the Type
attribute. Also, there's no way to enforce its presence on the API. That said, I may check if it is easy to include the attribute.