Configuring RACF for Kerberos

You must configure an external security manager, such as RACF®, to enable support for Kerberos.

Before you begin

Note: These instructions apply only to the use of local principals.

Before you perform this task, you must set up a Kerberos environment for z/OS® Security Server RACF by using the z/OS Integrated Security Services Network Authentication Service. For information on RACF, Kerberos and z/OS Integrated Security Services Network Authentication Service see z/OS Integrated Security Services Network Authentication Service Administration.

The configuration /etc/skrb/krb5.conf defines the local realm for the LPAR or sysplex.

The SKRBKDC started task must be running. For more information, see Setting up a Kerberos Key Distribution Center in z/OS Network File System Guide and Reference.

Procedure

  1. To set up CICS® to use Kerberos, you must first enable RACF protection for Kerberos. Activate RACF protection for the KERBLINK class by using the RACF SETROPTS command:
    SETROPTS CLASSACT(KERBLINK)
    For more information about the SETROPTS command, see z/OS Security Server RACF Command Language Reference.
  2. To set up a CICS region to use Kerberos, you must define a service principal name and associate it with the region user ID by using the ALTUSER command:
    ALTUSER region_id KERB(KERBNAME(service_principal))
  3. Define the client principal names to RACF by using the RDEFINE command:
    RDEFINE KERBLINK client_principal/realm
    For more information about KERBLINK profiles and automatic local principal name mapping, see z/OS Security Server RACF Security Administrator's Guide.
  4. Associate the client principal names with the region by using the PERMIT command:
    PERMIT client_principal/realm CLASS(KERBLINK) ID(region_id) ACCESS(READ) 
    For more information about the PERMIT command, see z/OS Security Server RACF Security Administrator's Guide.
  5. Associate a RACF user ID with the client principal by using the ALTUSER command:
    ALTUSER userid PASSWORD(password) NOEXPIRED KERB(KERBNAME(client_principal))
    Alternatively, you can associate a default user ID with all unassociated principals.
  6. In order for this to be activated a Kerberos key must be created. This is done automatically when the user next changes their password.


dfhws_configuring_racf_kerb.html | Timestamp icon Last updated: Sunday, 4 June 2017