SourceForge : Post

Project: Editor Discussion > REC:Secure Communication Profile 1.0 > Clarification/Rename for "MutualX509" conformance target > List of Posts

Forum Topic - Clarification/Rename for "MutualX509" conformance target: (2 Items)

View: as

Update

Duane Merrill

03/25/2008 12:17 PM

post5990

Clarification/Rename for "MutualX509" conformance target

The "MutualX509" policy is not technically "mutually-authenticated" in the sense that one might think.  It indicates 
that the message-sender is authenticated to the message-reciever.  In a request-response message exchange pattern, the 
remote resource is only authenticated to the initiator upon reciept of the response message.   While useful (
particularly as a foundation for holder-of-key authentication tokens), the policy name is misleading, and should 
probably be renamed.

Duane Merrill

05/01/2008 10:42 AM

post6016

Re: Clarification/Rename for "MutualX509" conformance target

Resolved: left as-is.  This is fine: the assertion must be applied at the operation or endpoint level and, as such, 
indicates that the message-senders during the message exchange must authenticate themselves using X.509 digital 
signature.

-Duane

Return