Which IIQ version are you inquiring about?
8.4p3
Hi at all,
In December, we upgraded our production environment from version 8.4p2 to 8.4p3.
The upgrade went smoothly, but we’re now noticing some features aren’t working.
For example, we noticed that the Targeted Access Review Live Report hadn’t been updated and was throwing an error when run because it was using deprecated functions. We loaded the template from another instance and the problem was resolved.
However, we’ve now encountered two cases that we can’t resolve.
- After the identity is created, a Modify is launched against the authoritative source (JDBC). The rule executes and works, but the related Provisioning Transaction isn’t generated. The modify request is launched in the PostJoiner with the following code:
ProvisioningPlan planUpdate = new ProvisioningPlan();
List listAttributeRequest = new ArrayList();
planUpdate.setIdentity(identity);
ProvisioningPlan.AccountRequest acctReq = new ProvisioningPlan.AccountRequest();
acctReq.setOperation(ProvisioningPlan.AccountRequest.Operation.Modify);
acctReq.setApplication(appName);
AttributeRequest attuserName = new AttributeRequest("username",ProvisioningPlan.Operation.Set,identityName);
listAttributeRequest.add(attuserName);
acctReq.setAttributeRequests(listAttributeRequest);
planUpdate.add(acctReq);
Provisioner provisioner = new Provisioner(context);
provisioner.execute(planUpdate);
and before the update, it correctly generated Provisioning transactions. Also, the failure to create the PT is only for this case and for this application, everything else works, the automatic ones and those created via rules.
- All ViewAccessXXXXXXX capabilities, introduced in version 8.4, that only allow viewing of debug pages do not work. If we assign one or more of these capabilities to a user or group, viewing of the read-only pages is not permitted. Everytime return Access Denied.
We’ve already checked the following SPRights files, but found no differences between the PRE and PRO environments.
identityiq/WEB-INF/config/authorization.xml
identityiq/WEB-INF/config/upgradeObjects.xml
identityiq/WEB-INF/config/webResources.xml
Both issues are not present in the pre-production environment, which has the same version (8.4p3), same configuration, same code and was followed the same update procedure as the production environment.
Is it possible that during the upgrade, some files or libraries in the installation were not updated correctly?
If so, can you tell us what to check to ensure all the required files have been updated?
Would reinstalling the patch fix the problem?
Thanks