Installation Guides › Implementation Guide › Implementation Overview › SOA Security Manager Overview › SOA Security Manager Architecture and Components › Data Stores › SOA Security Manager Key Database

Previous Topic: Session Store

Next Topic: Administrative User Interfaces

SOA Security Manager Key Database

(Optional) Some SOA Security Manager features and some SOA Security Manager product integrations require keys for signing, verifying, encrypting, and decrypting information. The purpose of the SOA Security Manager key database (smkeydatabase) is to make the private keys and the certificate authority (CA) certificates available to the environment.

The smkeydatabase is a separate component from a SOA Security Manager key store, and is a local, embedded database that does not require an external store.

For example, use of the SOA Security Manager Microsoft InfoCard authentication scheme and integrating SOA Security Manager with Federation Security Services are both examples of an implementation that require a smkeydatabase.

Note: For more information about a smkeydatabase, see the documentation roadmap.

More information:

SOA Security Manager Documentation