Propagating the Managed Reporting ID to the WebFOCUS Reporting Server

You may want to pass the authenticated Managed Reporting ID to the Reporting Server. For example, you may want to use it in report processing logic or to access data adapters. There are several ways in which to do this and limitations to be aware of, especially when the Reporting Server runs on Windows.

Reference: Passing the Managed Reporting ID as a Parameter

By adding the <set> IBIMR_user(pass) command to your site.wfs file, you can create a Dialogue Manager variable called IBIMR_user which you can use in a WebFOCUS request. This may be useful for echoing the user ID in a report heading, or for controlling processing flow with Dialogue Manager. You can also pass other Managed Reporting variables in this way. For information about Managed Reporting Variables, see Managed Reporting Internal Variables.

Reference: Making a Trusted Connection With the Managed Reporting ID

For all Reporting Server platforms except Windows, you can configure WebFOCUS and ReportCaster to make a trusted connection. Generally, this is used when both the Web server and Reporting Server share the same security system (such as on the Mainframe).

To configure the WebFOCUS Client to make a trusted connection to a non-Windows Reporting Server, set SECURITY=TRUSTED and TRUST_ID_SRC=IBIMR_user in the WebFOCUS Client odin.cfg file. To access these settings, go to the WebFOCUS Administration Console, select Reporting Servers, select Remote Services, select the desired Node in the Remote Services panel, then click Modify. In the Remote Services Modify Settings panel, select Trusted in the SECURITY drop-down list and two additional options are displayed. In the field next to the WebFOCUS script variable, which is selected by default, type IBIMR_user.

To configure ReportCaster to submit jobs to a non-Windows Reporting Server with a trusted connection based on the owner ID of the schedule, configure the following settings for each server node under Data Server in the WebFOCUS Server List of the ReportCaster Server Configuration tool:

Ensure that Run ID Type is set to USER.
Set Shared to YES and Trusted to PASSTHROUGH.

Reference: Connecting With the Managed Reporting ID

This configuration is useful when the Reporting Server is on Windows and the Trusted option is unavailable, and/or when you do not intend to create IDs on the Reporting Server. In either case, start the Reporting Server with the EDAEXTSEC=PTH option.

Set IBI_REPORT_USER=&IBIMR_user and leave IBI_REPORT_PASS blank using the WebFOCUS Administration Console in one of the following places depending on your needs:

If you want this behavior for all servers, configure the setting in the Reporting Server panel under Client Settings in the Configuration block.
If you want this behavior for a subset of your servers, create a WebFOCUS Client Node Profile for each server and put the settings in the node profiles. You can create or access these client-side profiles by clicking the Profile button under Remote Services in the Reporting Server block.

The connection ID will display in the edaprint log and in the Reporting Server console. However, because the Reporting Server does not authenticate the connection, you must take additional steps to protect against unauthorized access.

You can set the RESTRICT_TO_IP address setting in the Reporting Server to allow connection from the machines hosting the WebFOCUS Client and ReportCaster distribution server, for example, see WebFOCUS Reporting Server Security.

To configure ReportCaster to submit jobs to the Reporting Server with the ID of the job owner, configure the following settings in for each server node under Data Server, WebFOCUS Server List in the ReportCaster Server Configuration tool:

Ensure that Run ID Type is set to USER.
Ensure that Shared is set to YES and Trusted is set to NO.