Session Management Tasks
A session is a connection between your client and the Key Manager. At the start of each session, the client can authenticate itself by passing an NAE username and password OR an X.509 Client Certificate to the server.
Types of user
An authenticated user:
Has access to all global keys or KMIP keys (if KMIP session is used), all keys owned by the user, and all keys accessible to groups to which the user belongs.
Can create keys owned by the user, but cannot create global keys.
An unauthenticated user, also known as global user:
Has access to global keys only.
Can create global keys only.
Note
KMIP Sessions do not allow global users or unauthenticated users. The KMIP standard requires authentication.
When you access Key Manager as global user, don't pass username and password.
The decisions you make regarding authentication must be consistent with the NAE Port configurations. If your client attempts to connect with the Key Manager using an unsupported method, the session will be terminated. For example, if your client attempts to create a global session, but global sessions are disabled, the server closes the connection immediately. Review the NAE Port configurations before using the CADP for Java Provider.
Note
Keys are stored in the key cache. Cache are created per client, per session.
The NAE Port can be configured to allow clients to:
Create a global session.
Create a global session while using SSL.
Create an authenticated session using an NAE username and password.
Create an authenticated session using a SSL.
In this article you will learn how to:
