Sun Microsystems SunLink SNA 9.1 PU2.1, Configuration Manual

Page: 284 / 298

G-2 SunLink SNA 9.1 PU2.1 Server Configuration Guide—August 1997
G
G.2 Conversation-Level Security
Conversation-level security occurs after a session has been established between
two LUs. Whether the two LUs have used LU-LU verification during session
establishment is not important for conversation-level security. Conversation-
level security occurs when an allocation request is received by the partner LU.
An allocation request is generated when a program issues an (
MC_
) Attach verb
or a CPI-C Attach (
CMALLC
) call. The request is transmitted as an SNA Request
Unit (RU) containing a Function Management Header Type 5 (FMH-5), also
known as an Attach. Allocation requests can also occur as a result of an explicit
or implicit Change Number of Session (CNOS) request.
The Attach structure can contain the following access security information:
•
User ID
•
Password
•
Profile
•
Already Verified indicator
Already Verified indicates that the identity of the user has previously been
verified by the local LU. Since the partner LU trusts the local LU, no password
is sent.
The use of the user ID, password, and profile for conversation-level security
and Unix-level security is shown in the following figure.