Use cases for DSS-X client signatures

AC
by Assessorament CATCert0 views·Updated Feb 21, 2011
Powered by AI

Need to present on this topic?

Create your own polished presentation in minutes. Just describe what you need.

Free to try, no credit card required

Transcript

Use Cases

DSS-X client signatures

Signature Folder Application

Signature Folder App

DSS-X App

signatureRequest (Document_1, SigningCertificate_1)

signatureResponse(ID_1, SignedInfoDigest_1)

Use Case 1

signatureRequest (ID_1, RawSignature_1)

signatureResponse(ID_1, Signature_1)

App server

App server

Browser

Single document signature.

All signature inputs in the first signature request

For each document received in the Signature Folder Application, and even before the signer logs in, it sends a signature request to the DSS-X application with the document (could be the hash instead) and the x509 certificate linked to the user's private key that will perform the signature.

signatureRequest (Document_1, SignaturePolicy_1)

signatureResponse(ID_1, missingSignerAttr(signingCertificate, role))

signatureRequest (ID_1, signerAttr(signingCertificate, role))

signatureRequest (Document_1, SigningCertificate_1)

Documents to be signed

signatureResponse(ID_1, SignedInfoDigest_1)

Use Case 2

signatureRequest (ID_1, RawSignature_1)

ds:Signature

ds:SignedInfo

ds:Reference

SignedProperties

signatureResponse(ID_1, Signature_1)

ds:Reference

Document

ds:SignatureValue

The server creates the signature container using the elements provided in the request. Once the SignedInfo element is finished, performs the digest and prepares the response with the digest value to be signed.

ds:KeyInfo

ds:Object

QualifyingProperties

SignedProperties

SignedSignatureProperties

SigningTime

Signature Proc. IDs

SignedInfo Digests

SigningCertificate

Single document signature.

Not all signature attributes sent in the first request.

DSS server first response tells the client the missing attributes required to be present in the SignedProperties (rules defined in the SignaturePolicy, present in the request).

signatureResponse(ID_1, SignedInfoDigest_1)

signatureRequest (Document_1, SigningCertificate_1)

When application is loaded in browser, it retrieves document metadata, including SignedInfo digests.

signatureResponse(ID_1, SignedInfoDigest_1)

The response of the DSS-X server contains an ID to the started signature process and the SignedInfo digest to be signed locally. The Signature Folder Application must store this information to allow the local signature to be performed when the user selects a document to sign in the browser.

signatureRequest (Document_2, SigningCertificate_1)

signatureResponse(ID_2, SignedInfoDigest_2)

signatureRequest (Document_4, SigningCertificate_1)

Use Case 3

signatureResponse(ID_3, SignedInfoDigest_3)

Signatures /

Signed Documents

signatureRequest ((ID_1, RawSignature_1), (ID_2, RawSignature_2), (ID_3, RawSignature_3))

The SignatureValue retrieved from the user's side is sent back to the DSS-X server to update the signature container. The selection of the signature container to update is done by setting the process ID in the request.

SignatureValue of selected document's signature

signatureResponse((ID_1, RawSignature_1), (ID_2, RawSignature_2), (ID_3, Signature_3))

signatureRequest (ID_1, RawSignature_1)

Users /

X509 certificates

ds:Signature

Multiple documents signatures. A request is sent for each document.

The update of signature containers and the response with all the signatures can be done in a single request/response.

ds:SignedInfo

ds:Reference

SignedProperties

ds:Reference

Document

Unsigned Properties

ds:SignatureValue

The server creates the signature container using the elements provided in the request. Once the SignedInfo element is finished, performs the digest and prepares the response with the digest value to be signed.

ds:KeyInfo

The server updates the signature's basic form with the received SignatureValue, and completes the signature with the required unsigned properties (they could have been included in the request, or be the default ones specified in the server policy).

ds:Object

+

QualifyingProperties

Timestamps

CRL / OCSP

CA

SignedProperties

SignedSignatureProperties

SigningTime

SigningCertificate

signatureResponse(ID_1, Signature_1)

SignedInfo digest of selected document's signature

SignatureValue of selected document's signature

The signature, created using the selected signing certificate and proporties, is sent to the application in the signatureResponse.

hash

Local component to access signing device

raw Signature

The Signature Folder Application allows a user to access a document inbox, where documents to be signed can be selected and signed using a local device like a smartCard. The pseudo-protocol shown covers a simple use case where a single document is signed.