TERMINAL Class
Each record in the TERMINAL class defines a terminal of the local host, another host on the network, or an X terminal from which a login session can be made. A record also defines terminals that match a terminal name or IP address pattern (using wildcards). Terminal permissions are checked during the user login procedure, so that users cannot succeed in logging in from terminals they have not been authorized to use.
capamsc141
Each record in the TERMINAL class defines a terminal of the local host, another host on the network, or an X terminal from which a login session can be made. A record also defines terminals that match a terminal name or IP address
pattern
(using wildcards). Terminal permissions are checked during the user login procedure, so that users cannot succeed in logging in from terminals they have not been authorized to use.The TERMINAL class also controls administrative access. ADMIN users can only administer
PAM Server Control
from terminals for which they have appropriate access permissions.When you define a new TERMINAL record,
PAM Server Control
tries to convert the name you provide to a fully qualified name. If it succeeds, it stores the fully qualified name in the database. If it fails, it stores the name you specify. When you issue subsequent commands referencing this record (chres
, showres
, rmres
, authorize, and so on), use the name as it appears in the database.The key of the TERMINAL record is the name of the terminal. This name identifies the terminal to
PAM Server Control
.The following definitions describe the properties contained in this class record. Most properties are modifiable and can be manipulated using selang or the administration interfaces. Non-modifiable properties are marked
informational
.- ACLDefines a list of accessors (users and groups) permitted to access the resource, and the accessor access types. Each element in the Access Control List (ACL) contains the following information:
- AccessorDefines an accessor.
- AccessDefines the access authority that the accessor has to the resource.
- RAUDITDefines the types of access events thatPAM Server Controlrecords in the audit log. RAUDIT derives its name fromResourceAUDIT. Valid values are:
- allAll access requests
- successGranted access requests
- failureDenied access requests (default).
- noneNo access requests
PAM Server Controlrecords events on each attempted access to a resource. Whether the access rules were applied directly to the resource, group or class that had the resource as a member is not recorded.Use the audit parameter of thechresandchfilecommands to modify the audit mode. - CALACLDefines a list of the accessors (users and groups) that are permitted to access the resource, and their access types according to the Unicenter NSM calendar status.Each element in the calendar access control list (CALACL) contains the following information:
- AccessorDefines an accessor.
- CalendarDefines a reference to a calendar in Unicenter TNG.
- AccessDefines the access authority that the accessor has to the resource.
Use the calendar parameter with the authorize command to permit user or group access to the resource according to the access defined in the calendar ACL. - CALENDARRepresents a Unicenter TNG calendar object for user, group, and resource restrictions inPAM Server Control.PAM Server Controlfetches Unicenter TNG active calendars at specified time intervals.
- CATEGORYDefines one or more security categories assigned to a user or a resource.
- COMMENTDefines additional information that you want to include in the record.PAM Server Controldoes not use this information for authorization.Limit:255 characters
- CREATE_TIME(Informational) Displays the date and time when the record was created.
- DAYTIMEDefines the day and time restrictions that govern when an accessor can access a resource. Use the restrictions parameter with thechres,ch[x]usr, orch[x]grpcommands to modify this property.The resolution of daytime restrictions is one minute.
- GROUPSThe list of GTERMINAL or CONTAINER records a resource record belongs to.To modify this property in a TERMINAL class record, change the MEMBERS property in the appropriate CONTAINER or GTERMINAL record.Use themem+ormem-parameter with thechres,editres, ornewrescommand to modify this property.
- NACLTheNACLproperty of a resource is an access control list that defines the accessors with authorization denied to a resource, together with the type of access that they are denied (example, write). See also ACL, CALACL, PACL. Each entry in the NACL contains the following information:
- AccessorDefines an accessor.
- AccessDefines the type of access that is denied to the accessor.
deniedaccesscommand, or the authorize-deniedaccess-command, to modify this property. - NOTIFYDefines the user to be notified when a resource or user generates an audit event.PAM Server Controlcan email the audit record to the specified user.Limit:30 characters
- OWNERDefines the user or group that owns the record.
- PACL
- Defines a list of accessors that are permitted to access the resource when the access request is made by a specific program (or a program that matches a name-pattern) and their access types. Each element in the program Access Control List (PACL) contains the following information:
- AccessorDefines an accessor.
- ProgramDefines a reference to a record in the PROGRAM class, either specifically or by wildcard pattern matching.
- AccessDefines the access authority that the accessor has to the resource.Note:You can use wildcard characters to specify the resource in a PACL.
Use the via(
pgm
) parameter with the selang authorize command to add programs, accessors, and their access types to a PACL. You can use the authorize- command to remove accessors from a PACL.- SECLABELDefines the security label of a user or resource.Note:The SECLABEL property corresponds to the label[-] parameter of thechresandch[x]usrcommands.
- SECLEVELDefines the security level of an accessor or resource.Note:This property corresponds to the level[-] parameter of thech[x]usrandchrescommands.
- UACCDefines the default access authority for the resource. This indicates that the access is granted to accessors who are not defined toPAM Server Controlor who do not appear in the ACL of the resource.Use thedefaccessparameter with thechres,editres, ornewrescommand to modify this property.
- UPDATE_TIME(Informational) Displays the date and time when the record was last modified.
- UPDATE_WHO(Informational) Displays the administrator who performed the update.
- WARNINGSpecifies whether Warning mode is enabled. If Warning mode is enabled on a resource, then all access request to a resource is granted. If an access request violates an access rule, a record is written to the audit log.
Example 1:
This example shows how to authorize a user to access Selang on a terminal on the local host by using the TERMINAL class on a Unix/Linux endpoint. Follow these steps:
- Create a user "John".PAMSC> eu John password(John_Pwd)
- Log in as "John" user in a different terminal on the same local host, and try to execute Selang commands. John fails to access Selang because by default all users are not authorized to access Selang.ERROR: Initialization failed, EXITING! (localhost) ERROR: Login procedure failed ERROR: You are not allowed to administer this site from terminal MyLocalHost.sample.com
- The superuser (root) creates a policy using TERMINAL class that authorizes "John" to access Selang in a terminal on the local host.PAMSC> authorize TERMINAL MyLocalHost.sample.com uid(John) access(r w) (localhost)
- John attempts to access Selang in a terminal on the local host and succeeds.MyLocalHost.sample.com:~> /opt/CA/PAMSC/bin/selang CA PAMSC selang v12.81.0.2606 - CA PAMSC command line interpreter Copyright (c) YYYY CA. All rights reserved.
Example 2:
This example shows how to authorize a user to access Selang on a terminal on another host on the network by using the TERMINAL class on a Unix/Linux endpoint. Follow these steps:
- From the local host (MyLocalHost.sample.com), a root user logs in to another host (AnotherHost.sample.com) on the network.MyLocalHost.sample.com:~> ssh root@ AnotherHost.sample.com [email protected]'s password: # id uid=0(root) gid=0(system) groups=2(bin),3(sys),7(security),8(cron),10(audit),11(lp) # hostname AnotherHost.sample.com
- The root user accesses Selang, and creates a user “John” in another host on the network (AnotherHost.sample.com).# ./opt/CA/PAMSC/bin/selangPAMSC> eu John password(John_pwd)
- From the local host (MyLocalHost.sample.com), John user opens a terminal and logs in to another host (AnotherHost.sample.com) on the network, and attempts to access Selang but fails.MyLocalHost.sample.com:~> ssh John@ AnotherHost.sample.com [email protected]'s password: $ id uid=203(John) gid=1(staff) $ hostname AnotherHost.sample.com $ /opt/CA/PAMSC/bin/selang ERROR: Initialization failed, EXITING! (localhost) ERROR: Login procedure failed ERROR: You are not allowed to administer this site from terminal AnotherHost.sample.com
- The root user authorizes John to execute Selang commands in another terminal on the network.PAMSC> authorize terminal AnotherHost.sample.com uid(John) access(r w)
- John can now execute Selang commands in another terminal on the network.$ /opt/CA/PAMSC/bin/selangCA PAMSC selang v12.81.0.2690 - CA PAMSC command line interpreterCopyright (c) YYYY CA. All rights reserved.