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
Digital Certificate SupportThe syntax for using the REPLACE command to change a label follows:TSS REPLACE(acid|CERTAUTH|CERTSITE) {DIGICERT(name)}{SERIALNUM(serial number) ISSUERDN(issuer's dist' name)}LABLCERT(label name)An example for the LABLCERT command follows:TSS REPLACE(USER01) DIGICERT(DIGI0001) LABLCERT(‘label for digicert 002’)Removing a Certificate from a UserYou can use the REMOVE command to remove a certificate from a user.If the certificate has a connection to a user key ring, the certificate is removedalong with any key ring connections it can have.On a REMOVE command, the digital certificate can be identified three differentways: by using DIGICERT or LABLCERT, or by using both SERIALNUM andISSUERDN.Use the following command to remove a certificate from a user:TSS REM(acid|CERTAUTH|CERTSITE) {DIGICERT(8-byte name)}{LABLCERT(label name)}{SERIALNUM(serial number) ISSUERDN(issuer's dist' name)}An example for the REMOVE command follows:TSS REMOVE(USER01) DIGICERT(DIGI0001)Determining if a Certificate has been Added to eTrust CA-Top SecretYou can check to see who has a certificate in a specified data set. The CHKCERTcommand determines whether the digital certificate in the specified data set hasbeen added to the eTrust CA-Top Secret security file and associated with an acid.Use the following syntax for TSS CHKCERT:TSS CHKCERT DCDSN(input data-set-name) PKCSPASS(pksc12-password)DCDSN(input-data-set-name)—Specifies the name of an optional data set thatcontains the PKCS#10 certificate request data. The request data set name can bethe output from a TSS GENREQ command. The request data contains the user'sgenerated public key and X.509 distinguished name. The request data must besigned, DER-encoded, and then Base64 encoded according to PKCS#10 standard.PKCSPASS—The PKCS-password can be up to 255 characters, is case sensitive,and can contain blanks.1–64 Cookbook
Digital Certificate SupportImportant! The password associated with PKCS#12 certificates are notviewable. It is the eTrust CA-Top Secret administrator's responsibility to keep track ofthe PKCS#12 password that is assigned to the digital certificate.Exporting Certificates to Data SetsYou can export a certificate from a eTrust CA-Top Secret security file to a newdata set using the TSS EXPORT command. The certificate to be exported can beidentified by its DIGICERT name or by its label. You cannot export a digitalcertificate with ICSF.Use the following syntax for TSS EXPORT:TSS EXPORT(acid|CERTAUTH|CERTSITE){DIGICERT(name) {LABLCERT{up to 32 characters)}{DCDSN(output-data set name) FORMAT(format type)}{PKCSPASS(PKCS#12 password)}ACID—A user acid or you can specify:CERTAUTH—Is an acid in which your installation can maintain certificates thatwere generated by a third party certificate authority (CA). This acid ispre-defined in Top Secret or you can specify. You cannot add a KEYRING to thisACID.CERTSITE—Is an acid in which your installation can maintain site-generatedcertificates. This acid is pre-defined in Top Secret. You cannot add a KEYRING tothis ACID.DIGICERT—Specifies a one- to eight-character ID that identifies the certificatewith the user acid. The DIGICERT must be entered as part of all GENCERTcommands since this keyword indicates the name to be used in the digitalcertificate.DCDSN(output-data-set-name)—The data set will be allocated and cataloged,and will contain the output from the exported digital certificate. The data setname will conform to the MVS standards, up to a maximum of 26 characters.FORMAT—The following operands can be used with the FORMAT keyword:■■■■CERTB64—Indicates Base64 encoded certificates (default).CERTDER—Indicates DER encoded X.509 certificates.PKCS12B64—Indicates DER encoded (then Base64 encoded) PKCS#12package.PKCS12DER—Indicates DER encoded PKCS#12 package.An example for the FORMAT command follows:TSS EXPORT(USER01) DIGICERT(DIGI0001) DCDSN(USER3.CERT.DATA) FORMAT(CERTDER)Implementing eTrust CA-Top Secret in a z/OS or OS/390 Environment 1–65
- Page 23 and 24: OpenEdition MVS / UNIX System Servi
- Page 25 and 26: OpenEdition MVS / UNIX System Servi
- Page 27 and 28: OpenEdition MVS / UNIX System Servi
- Page 29 and 30: OpenEdition MVS / UNIX System Servi
- Page 31 and 32: Tracing UNIX System Services (OMVS)
- Page 33 and 34: Tracing UNIX System Services (OMVS)
- Page 35 and 36: Tracing UNIX System Services (OMVS)
- Page 37 and 38: Tracing UNIX System Services (OMVS)
- Page 39 and 40: Using TCP/IPFILE AUDIT OPTIONS—Th
- Page 41 and 42: Using TCP/IPwheresysname is the nam
- Page 43 and 44: Using FTPHow to Secure FTPFTP runs
- Page 45 and 46: Using TELNETTerminal Source Restric
- Page 47 and 48: WebSphere Application Server for z/
- Page 49 and 50: WebSphere Application Server for z/
- Page 51 and 52: WebSphere Application Server for z/
- Page 53 and 54: WebSphere Application Server for z/
- Page 55 and 56: WebSphere Application Server for z/
- Page 57 and 58: Lotus Domino Go Webserver/* PERMITT
- Page 59 and 60: Lotus Domino Go WebserverTo disable
- Page 61 and 62: Lotus Notes and Novell Directory Se
- Page 63 and 64: Digital Certificate SupportGeneral
- Page 65 and 66: Digital Certificate SupportFOR|UNTI
- Page 67 and 68: Digital Certificate SupportDCDSN(re
- Page 69 and 70: Digital Certificate SupportNote: In
- Page 71 and 72: Digital Certificate SupportYou can
- Page 73: Digital Certificate SupportCase #2.
- Page 77 and 78: Digital Certificate SupportAdding a
- Page 79 and 80: Digital Certificate SupportReconnec
- Page 81 and 82: Digital Certificate SupportTSS LIST
- Page 83 and 84: Certificate Name Filtering SupportT
- Page 85 and 86: Certificate Name Filtering SupportI
- Page 87 and 88: Certificate Name Filtering SupportD
- Page 89 and 90: Certificate Name Filtering SupportL
- Page 91 and 92: KerberosKerberosetrust CA-Top Secre
- Page 93 and 94: KerberosThe command syntax for this
- Page 95 and 96: KerberosThe following command creat
- Page 97 and 98: Mapping of Foreign EnvironmentsMapp
- Page 99 and 100: Mapping of Foreign EnvironmentsMapp
- Page 101 and 102: Distributed File Server SMB SUPPORT
- Page 103 and 104: NFS (Network File System)The first
- Page 105 and 106: z/OS and OS/390 Security Server Sup
- Page 107 and 108: z/OS and OS/390 Security Server Sup
- Page 109 and 110: z/OS and OS/390 Security Server Sup
- Page 111 and 112: Chapter2Controlling Access to theHi
- Page 113 and 114: Controlling HFS Using the Native UN
- Page 115 and 116: Controlling HFS Using CA SAF HFS Se
- Page 117 and 118: Securing HFS FunctionsKeywordALLCON
- Page 119 and 120: Securing HFS FunctionsFile Function
- Page 121 and 122: Implementing CA SAF HFS SecurityImp
- Page 123 and 124: HFSSEC Control Option+12—The addr
Digital Certificate SupportImportant! The password associated with PKCS#12 certificates are notviewable. It is the <strong>eTrust</strong> <strong>CA</strong>-<strong>Top</strong> <strong>Secret</strong> administrator's responsibility to keep track ofthe PKCS#12 password that is assigned to the digital certificate.Exporting Certificates to Data SetsYou can export a certificate from a <strong>eTrust</strong> <strong>CA</strong>-<strong>Top</strong> <strong>Secret</strong> security file to a newdata set using the TSS EXPORT comm<strong>and</strong>. The certificate to be exported can beidentified by its DIGICERT name or by its label. You cannot export a digitalcertificate with ICSF.Use the following syntax <strong>for</strong> TSS EXPORT:TSS EXPORT(acid|CERTAUTH|CERTSITE){DIGICERT(name) {LABLCERT{up to 32 characters)}{DCDSN(output-data set name) FORMAT(<strong>for</strong>mat type)}{PKCSPASS(PKCS#12 password)}ACID—A user acid or you can specify:CERTAUTH—Is an acid in which your installation can maintain certificates thatwere generated by a third party certificate authority (<strong>CA</strong>). This acid ispre-defined in <strong>Top</strong> <strong>Secret</strong> or you can specify. You cannot add a KEYRING to thisACID.CERTSITE—Is an acid in which your installation can maintain site-generatedcertificates. This acid is pre-defined in <strong>Top</strong> <strong>Secret</strong>. You cannot add a KEYRING tothis ACID.DIGICERT—Specifies a one- to eight-character ID that identifies the certificatewith the user acid. The DIGICERT must be entered as part of all GENCERTcomm<strong>and</strong>s since this keyword indicates the name to be used in the digitalcertificate.DCDSN(output-data-set-name)—The data set will be allocated <strong>and</strong> cataloged,<strong>and</strong> will contain the output from the exported digital certificate. The data setname will con<strong>for</strong>m to the MVS st<strong>and</strong>ards, up to a maximum of 26 characters.FORMAT—The following oper<strong>and</strong>s can be used with the FORMAT keyword:■■■■CERTB64—Indicates Base64 encoded certificates (default).CERTDER—Indicates DER encoded X.509 certificates.PKCS12B64—Indicates DER encoded (then Base64 encoded) PKCS#12package.PKCS12DER—Indicates DER encoded PKCS#12 package.An example <strong>for</strong> the FORMAT comm<strong>and</strong> follows:TSS EXPORT(USER01) DIGICERT(DIGI0001) DCDSN(USER3.CERT.DATA) FORMAT(CERTDER)Implementing <strong>eTrust</strong> <strong>CA</strong>-<strong>Top</strong> <strong>Secret</strong> in a z/<strong>OS</strong> or <strong>OS</strong>/390 Environment 1–65