8.2 Assumptions

The business requirements, as depicted in Use Case diagrams and Sequence Diagrams, have been simplified for instructional purposes. The sample physical architecture and future deployment architecture diagrams are for illustration purposes, and they do not trace back to business requirements.

For the definition and technology details of JAXM (asynchronous XML messaging) and JAX-RPC (synchronous Web Services), please refer to Chapter 3, Web Services Technology Overview. For the definition and technology details of WS-Security (XML encryption and digital signature for SOAP Messaging) and SAML protocol (a Single Sign-on security protocol), please refer to Chapter 7, Web Services Security.

A sample "key store" (sample_soap_keystore) is placed in the secure message services (aka server key store) and requester (aka client key store) directories. The sample key store is an asymmetric key pair generated for the purpose of demonstrating the use of XML Encryption and digital signature for secure messaging. It comes with VeriSign's Trust Service Integration Kit (TSIK) and stores user credentials (in this case, a valid digital certificate for the MMC entity). For details, please refer to the TSIK documentation. (VeriSign's TSIK is a security toolkit for developing XML Key Management and WS-Security. Refer to Chapter 7, Web Services Security, for more details.)

Netegrity's TSIK is used in this case study to provide secure message services (WS-Security) for SOAP messages in the data transport layer. Refer to Chapter 7, Web Services Security, for details. This denotes that a client request using SOAP messaging will be encrypted and digitally signed with valid security tokens to ensure data integrity, confidentiality, and non- repudiation .