Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

Version 1 Next »

Universal Broker Digital Certificate (RACF) Set-up

Setting up a digital certificate infrastructure in a production environment for the first time requires careful planning by the Security organization and Universal Agent administrator. The instructions provided on this page have been simplified for illustration purposes.

You work with RACF Digital Certificates using the RACF command RACDCERT. RACF profiles control access to the functions provided by RACDCERT.

The user profile with which the following commands are executed require either:

  • SPECIAL attribute
  • Appropriate access to the IRR.DIGTCERT.function profile in the FACILITY class.
    • READ access is required to IRR.DIGTCERT.function to issue RACDCERT commands for the executing user.
    • UPDATE access is required to IRR.DIGTCERT.function to issue RACDCERT commands for other users.
    • CONTROL access is required to IRR.DIGTCERT.function to issue RACDCERT command for SITE or CERTAUTH certificates.

The member UNVINDC in the INSTALL library contains the JCL to execute the RACF commands listed in the following steps.

Step 1

Create a Certificate Authority (CA) certificate and private key using the following RACDCERT command:
 

RACDCERT CERTAUTH GENCERT +
   SUBJECTSDN(CN('Certificate Authority') +
      OU('Security') +
      O('Company Name, Inc.') +
      C('US')) +
   NOTAFTER(DATE(2030-01-01)) +
   *KEYUSAGE(HANDSHAKE CERTSIGN) +
   WITHLABEL('Company CA')

Change the subject and label names to meet local requirements.
 

Step 2

Create a certificate for the Universal Broker STC and sign it with the CA certificate created in Step 1 using the following RACDCERT command:
 

RACDCERT ID(UBRUSR) GENCERT +
   SUBJECTSDN(CN('broker.company.com') +
      OU('Operations') +
      O('Company Name, Inc.') +
      C('US')) +
   KEYUSAGE(HANDSHAKE) +
   WITHLABEL('Broker') +
   SIGNWITH(CERTAUTH LABEL('Company CA')

Change the subject and label names to meet local requirements. The subject's Common Name (CN) value should uniquely identify this instance of the broker in the enterprise.
 

Step 3

Create a certificate key ring for the user profile UBRUSR with the following RACDCERT command:
 

RACDCERT ID(UBRUSR) ADDRING(BROKER)

Step 4

Connect the CA certificate and the Universal Broker certificate to the key ring with the following RACDCERT command:
 

RACDCERT ID(UBRUSR) CONNECT(CERTAUTH LABEL('Company CA') +
   RING(BROKER)
RACDCERT ID(UBRUSR) CONNECT(LABEL('Broker') RING(BROKER) DEFAULT)

Change the labels to match the values used in previous steps.
 

Step 5

If the resource profile IRR.DIGTCERT.LISTRING in the FACILITY class is not defined, define it with the following RDEFINE command:
 

RDEFINE FACILITY (IRR.DIGTCERT.LISTRING) UACC(NONE)

Step 6

Permit the Broker user profile UBRUSR READ access to the RACF profile IRR.DIGTCERT.LISTRING in the FACILITY class using the following PERMIT command:
 

PE IRR.DIGTCERT.LISTRING CLASS(FACILITY) ID(UBRUSR) ACCESS(READ)

Step 7

Modify the Universal Broker configuration member UBRCFG00 as follows:
 

ssl_implementation   system
saf_key_ring        BROKER

Step 8

The CA certificate must be distributed to the remote systems from which Universal Agent managers are executed. The managers must be configured with the CA certificate in their list of Trusted CA certificates using the CA_CERTIFICATES configuration option.
 
The CA certificate is exported out of the RACF data base into a data set in a PEM (or base64) format with the following RACDCERT command:
 

RACDCERT CERTAUTH EXPORT (LABEL('Company CA')) +
   DSN(TEST.CA.CERT) FORMAT(CERTB64)

 
Change the label to match the value used in previous steps.
 
The tsoprefix.TEST.CA.CERT data set contains a PEM formatted certificate. The format is a text format that transfers safely across the network in text mode.
 
Note that the CA private key is not exported. The CA certificate does not contain any private data.

  • No labels