Sun Microsystems SunLink SNA 9.1 PU2.1, Руководство по настройке

Страница: 286 / 298

G-4 SunLink SNA 9.1 PU2.1 Server Configuration Guide—August 1997
G
G.3 Security Access Verification
If the Attach contains security information and it is determined that the LU has
a security restriction, parameters in the Attach are matched again those in the
LU security list.
You specify the minimum security required for LU-LU sessions in the partner
LU definition, as follows:
•
None - An Attach is rejected if any security parameters are present.
•
Conversation - Any request containing security, but not an Already Verified
indicator, is verified against the LU security list. The Attach is verified if an
entry in the security list matches all the security fields in the Attach.
Otherwise, the request is rejected.
•
Already Verified - The Attach is checked for both Conversation and Already
Verified and is not checked for a password.
If no security parameters are defined for an LU (no security parameters are
contained in the Attach and the partner LU expects no security), the Attach is
passed to resource verification. Otherwise, the Attach is rejected.
G.4 Resource Access Verification
If you want to further control access to the TP, you can perform resource access
verification against the TP resource access list after security access. Each TP has
one resource access list.
The following levels of access security are supported:
•
None
- No verification is required. However, if security parameters are
received, conversation-level checks are performed.
•
Conversation - Conversation-level checks are performed. Resource access
verification is not performed.
•
User ID - The user ID must exist in the TP resource access list.
•
Profile
- The profile must exist in the TP resource access list.
•
User ID and profile - Both the user ID and profile must exist in the TP
resource access list.