[OASIS Issue Tracker] (DSSX-15) There should be mechanism for passing constraints to the serve

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/DSSX-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=65723#comment-65723 ] 

Juan Cruellas commented on DSSX-15:
-----------------------------------

Thanks Detlef,

I tend to agree with you in that the constraints are closely related to the signature policy. 
Just one question, if one wants that a signature is validated using a certain signature policy that has identifier (URI or OID), and that is well known within the community one appertains, there would be enough to include the identifier of the signature policy in the request, without any constraint indication: the identifier should allow the server to identify the signature policy and allow the server to identify what constraints it has to apply (as the signature policy document would actually indicate all these constraints )

The constraints should appear in the DSS request only when one wants that the server validates a signature against a certain signature policy and also some additional constraints, or when one does not want that the server validates a signature against any known and defined signature policy but against a sequence of specific constraints.

May I propose that the profile that specifies the protocol for requesting generation and valildation of a signature against a certain signature policy also includes the specification of the elements for identifying constraints?




> There should be mechanism for passing constraints to the serve
> --------------------------------------------------------------
>
>                 Key: DSSX-15
>                 URL: https://issues.oasis-open.org/browse/DSSX-15
>             Project: OASIS Digital Signature Services eXtended (DSS-X) TC
>          Issue Type: Bug
>          Components: Core
>            Reporter: Juan Cruellas
>            Assignee: Stefan Hagen
>
> 4. Constraints.
> There should be some mechanism for passing constraints to the server. Should this appear into the core?



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)