eTrust CA-Top Secret Security for z/OS and OS ... - SupportConnect

eTrust CA-Top Secret Security for z/OS and OS ... - SupportConnect eTrust CA-Top Secret Security for z/OS and OS ... - SupportConnect

supportconnectw.ca.com
from supportconnectw.ca.com More from this publisher
12.07.2015 Views

KerberosThe Kerberos password of this realm is children. The default ticket life is 10hours, a minimum ticket life of 30 seconds, and a maximum ticket life of 24hours.Defining Local PrincipalsLocal principals in Kerberos are user acids capable of activity on Unix SystemsServices, who are able to initiate Kerberos commands in the systemcorresponding to the local realm. Kerberos local principals clearly must possessat least the following with sufficient authority to allow access to the OMVS orISHELL shells.■■■■■UIDGROUPDFLTGRPHOMEOMVSPGMWhen a local principal is defined, the affected ACID receives a KERB segment tohold relevant information, some of which will not be available for display. Acorresponding KERBSEGM record will also be defined to the SDT. The label forthe KERBSEGM record is the ACID to which the new segment has been added.The administrator defines Kerberos information for the user as follows:TSS ADD(acid) KERBNAME(principal_name) acid —Specifies the security ACID to be defined with Kerberos information.principal_name—Specifies the Kerberos Principal Name associated with thisuser. This information is added to the KERB segment of the user’s securityrecord. It is also added to the SDT KERBNAME record for high-speedcross-reference indexing. The KERBNAME specified must be unique for eachuser in the local realm. KERBNAME cannot be added to a PROFILE or GROUPACID, nor can it be added to a hierarchy ACID. The fully qualified Kerberosprincipal name is formatted from the KERBDFLT REALMNAME and theKERBNAME principal_name. The combined length cannot exceed 240characters. The principal name cannot include spaces (x’40’) or the “at” sign(x’7F’)./…/local_realm/principal_nameinterval—Specifies the maximum ticket life associated with tickets for this user.The range of available values is 1 – (2**31 – 1). Sensible values for this parametershould not exceed MAXTKTLF for the REALM, and should not be exceeded bythe REALM DEFTKTLF.1–84 Cookbook

KerberosThe following command creates a KERBNAME field “boris_baddenof” within anew KERB segment on “useracid” Notice that no MAXTKTLF operand has beensupplied in this command.TSS ADD(useracid) KERBNAME(boris_baddenof)The KERB segment may be displayed by using the following LIST command:TSS LIST(useracid) SEGMENT(KERB)The corresponding KERBSEGM SDT record can be viewed with the followingcommand:TSS LIST(SDT) KERBSEGM(useracid)Password Change Server ACIDKerberos requires the creation of a Password Change Server ACID with areserved local principal name. There is no requirement on the characteristics ofthe ACID other than that the user have local principal name kadmin/changepw.During testing we defined a USS capable user as follows:TSS CREATE(KRBCHG) DEPT(sysdept) NAME(‘KERBEROS PSWD/CHG’) PASS(pswd,0)FAC(STC,BATCH)TSS ADD(KRBCHG) UID(…)TSS ADD(KRBCHG) GROUP(OMVSGRP) DFLTGRP(OMVSGRP)TSS ADD(KRBCHG) HOME(/u/krbchg) OMVSPGM(/bin/sh)TSS PER(KRBCHG) HFSSEC(/u.krbchg) ACC(READ,UPDATE,EXEC)TSS PER(KRBCHG) HFSSEC(/BIN.SH) ACC(READ,EXEC)TSS ADD(KRBCHNG) KERBNAME(kadmin/changepw)Preparing Local Principal ACIDs for KerberosSYSEXEC changesThe following data set needs to be added to the TSO SYSEXEC DD statement ofthe Kerberos user’s TSO procedure:EUVF.SEUVFEXC.profile changesChanges are required for Kerberos user’s .profile file in their home directory.These changes may optionally be added to the /etc/.profile file. The followingdirectory must be placed as the first directory in the PATH variable, so that itoverrides DCE./usr/lpp/skrb/binImplementing eTrust CA-Top Secret in a z/OS or OS/390 Environment 1–85

KerberosThe Kerberos password of this realm is children. The default ticket life is 10hours, a minimum ticket life of 30 seconds, <strong>and</strong> a maximum ticket life of 24hours.Defining Local PrincipalsLocal principals in Kerberos are user acids capable of activity on Unix SystemsServices, who are able to initiate Kerberos comm<strong>and</strong>s in the systemcorresponding to the local realm. Kerberos local principals clearly must possessat least the following with sufficient authority to allow access to the OMVS orISHELL shells.■■■■■UIDGROUPDFLTGRPHOMEOMVSPGMWhen a local principal is defined, the affected ACID receives a KERB segment tohold relevant in<strong>for</strong>mation, some of which will not be available <strong>for</strong> display. Acorresponding KERBSEGM record will also be defined to the SDT. The label <strong>for</strong>the KERBSEGM record is the ACID to which the new segment has been added.The administrator defines Kerberos in<strong>for</strong>mation <strong>for</strong> the user as follows:TSS ADD(acid) KERBNAME(principal_name) acid —Specifies the security ACID to be defined with Kerberos in<strong>for</strong>mation.principal_name—Specifies the Kerberos Principal Name associated with thisuser. This in<strong>for</strong>mation is added to the KERB segment of the user’s securityrecord. It is also added to the SDT KERBNAME record <strong>for</strong> high-speedcross-reference indexing. The KERBNAME specified must be unique <strong>for</strong> eachuser in the local realm. KERBNAME cannot be added to a PROFILE or GROUPACID, nor can it be added to a hierarchy ACID. The fully qualified Kerberosprincipal name is <strong>for</strong>matted from the KERBDFLT REALMNAME <strong>and</strong> theKERBNAME principal_name. The combined length cannot exceed 240characters. The principal name cannot include spaces (x’40’) or the “at” sign(x’7F’)./…/local_realm/principal_nameinterval—Specifies the maximum ticket life associated with tickets <strong>for</strong> this user.The range of available values is 1 – (2**31 – 1). Sensible values <strong>for</strong> this parametershould not exceed MAXTKTLF <strong>for</strong> the REALM, <strong>and</strong> should not be exceeded bythe REALM DEFTKTLF.1–84 Cookbook

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!