Read-only session states

A read-only session can be in one of two states, as illustrated in the following figure. When the session is initially opened, it is in either the "R/O Public Session" state (if the application has no previously open sessions that are logged in) or the "R/O User Functions" state (if the application already has an open session that is logged in). Note that read-only SO sessions do not exist.

Figure 3, Read-Only Session States

The following table describes the session states:

Table 4, Read-Only Session States
State Description

R/O Public Session The application has opened a read-only session. The application has read-only access to public token objects and read/write access to public session objects.

R/O User Functions The normal user has been authenticated to the token. The application has read-only access to all token objects (public or private) and read/write access to all session objects (public or private).

RSA Security Inc. Public-Key Cryptography Standards - PKCS#11 - v220

State	Description
R/O Public Session	The application has opened a read-only session. The application has read-only access to public token objects and read/write access to public session objects.
R/O User Functions	The normal user has been authenticated to the token. The application has read-only access to all token objects (public or private) and read/write access to all session objects (public or private).