Configure Mutual SSL Between MashZone NextGen and Mashable Information Sources

Both the information source and MashZone NextGen exchange certificates.

Note: For mashups, you must use the <invoke> statement to connect to information sources that require mutual SSL. The <directinvoke> statement in EMML only supports one-way SSL connections.

This scenario uses the SSL security profile that is provided in MashZone NextGen. It requires:

Store and Certificates:

A certificate store as key store and trust store for the MashZone NextGen Server.

A key certificate pair for the MashZone NextGen Server.

Public certificates in the trust store for any information sources that have self-signed certificates.

You must add self-signed certificates to the trust store before the mashable information source can be registered. See Trusted Peer Cerficates for more information.

See The Certificate Store and Certificates for instructions.

Configuration in MashZone NextGen for both the key store and trust store. See Configure Certificate Stores in MashZone NextGen for instructions.

Security Profile configuration for each mashable information source. You provide this configuration when you register the mashable. See Mashable Authentication with Security Profiles for more information.