Private registry and credentials

This section does not apply to the C code base.

As every entity needs its own credentials to be authenticated, we need to know:
  1. How to execute registration to get the credentials
  2. Where to manage the credentials in a secure manner

The private registry enables the secure management of an entity's private credentials, and the public registry manages the set of public credentials.

The private registry provides a base registry with secure or cryptographic tokens. For example, it can be a secure repository for public elements like mini-certificates, and private elements like private keys.

The private registry allows only authorized users to access the private elements. Normally, only the legitimate queue manager user can access the registry using a PIN. However, configuration options enable you to bypass this if you are not overly concerned with security issues.

The private registry provides support for services, for example digital signature and RSA decryption, in such a way that the private objects never leave the private registry. By providing a common interface, it hides the underlying device support, which currently is restricted to the local file system.

See Security for more detailed information on the private registry and credentials.


Terms of use | WebSphere software

(c) Copyright IBM Corporation 2004, 2005. All rights reserved.