Identity Governance: unable to integrate the JasperReports Server for Reporting - 8.1 - User is Unauthorized to access the resource
search cancel

Identity Governance: unable to integrate the JasperReports Server for Reporting - 8.1 - User is Unauthorized to access the resource

book

Article ID: 264954

calendar_today

Updated On:

Products

CA Identity Suite CA Identity Governance

Issue/Introduction

The customer is running the standalone version of Identity Governance 14.4 CP2 and has recently upgraded the Jaspersoft Report Server to version 8.1.

As described in the upgrade process, the connection from the Identity Governance to the Jaspersoft Report server must be reconfigured:

https://techdocs.broadcom.com/us/en/symantec-security-software/identity-security/identity-governance/14-4/administrating/Enterprise-Reporting/Integration-with-JasperReports-Server-for-Reporting---8-1-or-8-2.html

The connection can be tested successfully:

However, when it comes to saving such configuration, the following error is observed:

 

Environment

Release: 14.4,14.5

Cause

The customer had an issue with integrating IG with Jasper Reports due to "User is Unauthorized to access the resources."

We checked a couple of ways to resolve the issue:

https://knowledge.broadcom.com/external/article?articleId=141674

https://techdocs.broadcom.com/us/en/symantec-security-software/identity-security/identity-governance/14-4/administrating/Enterprise-Reporting/Troubleshooting-for-Reporting.html

Please be aware that with properly configured Jasper IG will create a user by itself during integration.

Resolution

Broadcom documentation was not followed but Tibco guide:

https://techdocs.broadcom.com/us/en/symantec-security-software/identity-security/identity-governance/14-4/installing/Install-Symantec-IGA-JasperReports-Server---8-1-or-8-2.html

Since the customer's installation was done in such a way step 2.d was not performed and the installation script: brcm-js-install.bat from buildomatic folder was not run.

After running it and redoing the integration everything works fine.

You will need to comment out line 9 in the file starting from CALL.