Configuring identity propagation for web service requests into CICS using WebSphere DataPower

In this scenario, you will configure identity propagation for web service requests sent from WebSphere® Application Server to CICS from a WebSphere DataPower® XI50, Version 3.8 integration appliance.

Before you begin

Ensure you have the correct levels of software. See Identity propagation requirements for the minimum software levels.

You must configure your RACF RACMAP settings before you configure your web service connections. See Configuring identity propagation with RACF.

About this task

You can use a WebSphere DataPower appliance with CICS web services to provide security, for example, as an XML firewall, and to perform expensive and complex processing of XML messages, for example, processing an XML digital signature.
Figure 1. A WebSphere DataPower XI50 appliance linking service requesters and CICS applications

This scenario modifies an existing XML firewall policy in WebSphere DataPower to allow identity propagation information to flow to CICS. In this scenario, you do not need to change existing WebSphere Application Server settings. You will edit your existing WebSphere DataPower post-processing settings, so that WebSphere DataPower retrieves the user credentials (X.500 distinguished name and associated LDAP realm) from the LDAP server and maps them to a z/OS ICRX identity token, which identifies the distributed identity of a user. For more information about ICRX identity tokens, see z/OS Security Server RACF Data Areas.
Figure 2. Configuring Websphere DataPower to communicate with CICS using a web service request.

Procedure

  1. Log on to the WebSphere DataPower XI50, Version 3.8 appliance, using the web-based graphical user interface (WebGUI) and display the DataPower Control Panel.
  2. Select Objects, and the AAA (Authentication, Authorization, and Audit) policy from the XML processing section. Existing policies are displayed.
  3. To configure the AAA policy, select the policy that you want to enable for identity propagation, and select the PostProcessing tab. A screen is displayed, which shows options to generate an ICRX token for z/OS identity propagation and a field to enter an ICRX realm:
    Figure 3. WebSphere DataPower PostProcessing screen
  4. Select the on radio button for the Generate an ICRX token for z/OS identity propagation option. Do not select more than one radio button.
  5. In the ICRX realm field, type the LDAP realm name, preserving the correct case of the realm. The X.500 distinguished name is extracted from the LDAP server, however you must enter the realm name because it is not detected by WebSphere DataPower. Use the correct case when entering the realm name, because RACF processing is case sensitive.
  6. Save your changes by clicking the Apply button.

Results

When WebSphere DataPower receives a request from a web service client, it generates an ICRX identity token from the credentials that you have specified in the AAA policy and passes these to CICS. The ICRX identity token identifies the distributed identity of the user.

What to do next

If you have not already configured your CICS PIPELINE configuration file to expect an ICRX identity token, see Configuring provider mode web services for identity propagation.


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