Profile

Hi, The proof-of-concept message-level security profile for Core 2 looks as follows: Defines message-level security for OptionalInput. A unique identifier for this message. Message should only be used within this time frame. The URL to which ...

Hi Andreas, Because we are using DSS Core over Browser POST in our DSS implementation, we really need message-level security by means of an XML signature. Hence our SignRequest looks as follows: d2hlcmUgZG8gSSBwdXQgbXkgWE1MIHNpZ25hdHVyZT8= hello world message-identifier created-value ...

Hi Andreas, There seems to be an error in your rewritten xmldsig-core-schema. It can no longer validate XML signatures: cvc-complex-type.2.4.a: Invalid content was found starting with element 'ds:SignedInfo'. One of '(" http://www.w3.org/2000/09/xmldsig#":SignatureValue) ' is expected. Kind Regards, ...

Hi Andreas, Adding a new profile with Core 1, a DSS vendor just had to import the XSD within the WSDL, and in the code could do something like: AnyType optionalInputs = signRequest.getOptionalInputs(); for (Object optionalInput : optionalInputs.getAny()) ( if (optionalInput instanceof JAXBElement) ( ...

Hi Detlef, Yes! :) Kind Regards, Frank. > Op 30 jan. 2018, om 10:21 heeft Dr. Detlef Hühnlein het volgende geschreven: > > Hi Frank, > > how about “security relies both on the security of the TLS-channel and the signature of the Assertion/ Response, > if these data flow through the User Agent”? … The ...