Conversation, as defined here, is a purely technical issue. Its specification in the implementation framework allows a common technical dialog between trading partners across all business processes. Continually redefining the conversation in each individual business process is a mistake that very quickly leads to inconsistency and implementation complexity. Security Security and integrity of the information carried in B2B messages are of paramount importance. The implementation framework defines exactly what security measures are allowed and how they are applied.
Authentication enables the receiver of a message to verify the sender's identity.
In some cases, authentication is defined as an extension of the protocol, such as SSL, while in others it is defined as part of the implementation framework conversation. Non-repudiation does not allow the sender of a message to deny involvement in the creation of a message. Providing non-repudiation usually involves some combination of digital certificates and digital signatures. Authorization is the process by which a receiver ensures that the sender of a message has sufficient rights to make a particular request. Normally, authorization is closely tied to the authentication mechanism to obtain partner identity before verifying rights via some access control list.