OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-caf message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [Bug 258] New: use of WS-Security


http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=258

           Summary: use of WS-Security
           Product: General
           Version: 1.0
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: WSDL
        AssignedTo: ws-caf@lists.oasis-open.org
        ReportedBy: mark.little@arjuna.com
         QAContact: mark.little@arjuna.com


Tony notes that assertion type doesn't include wsu:id attribute anymore. 
Issue filed.

Assertion never did have wsu:id, so it was agreed that this wasn't the issue.
However, the question is: why don't we sign all messages? What is the precedent
for this? Do we need to handle it or is it more a composability issue that has
to be decided "globally".



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]