ReportCaster Credentials

ReportCaster security is based primarily on authenticating the following credentials.

ReportCaster user ID (owner ID). This user ID and password enables users to access ReportCaster.

If ReportCaster is licensed with Managed Reporting, ReportCaster owner credentials are created and maintained using the Managed Reporting Administration Interface. In this case, the Managed Reporting credentials are the same as the ReportCaster owner credentials. If you successfully log on to Managed Reporting, you do not need to again supply the ReportCaster owner credentials when accessing ReportCaster, since your security credentials will have already been authenticated by Managed Reporting.

If ReportCaster is not licensed with Managed Reporting, ReportCaster owner credentials are created and maintained using the User Administrator tool in the ReportCaster Development and Administration Interface.

Execution ID. A user ID that is used to run a scheduled Task on a specified server. Execution credentials can be created and maintained using the Execution ID menu option in the ReportCaster Console. For more information, see the ReportCaster Development and Library Content manual.

Note: A schedule that includes multiple Tasks may include multiple Execution IDs. However, there can only be one ReportCaster user ID for each schedule.

ReportCaster Security Cookies

Before accessing ReportCaster, a valid sign-on must take place. A successful sign-on results in the setting of one or more of the following security cookies:

WF_COOKIE contains the Execution ID of the user and password for each server to which the user has logged on. This cookie is set when IBIWF_action=WF_SIGNON is specified on the sign-on request.
MR_COOKIE contains the Managed Reporting user ID of the user. This cookie is set when IBIMR_action=MR_SIGNON is specified on the sign-on request.
RC_COOKIE contains the ReportCaster user ID of the user. If ReportCaster is configured with Managed Reporting, and you access ReportCaster from Managed Reporting, RC_COOKIE is generated from MR_COOKIE.

These cookies are always encrypted and expire at the end of the session. For more information about strengthening the encryption algorithm used to protect the ReportCaster cookie, see Optional Encryption Providers for ReportCaster.