There is currently no work around for this. The Vendor complied the current Policy Manager with dynamic libraries that cause the Policy manager to go to Adobe to retrieve them . We at EMC are aware of the problem and have escalated it to the vendor - and it is fixed in their current release generic release of Policy Manager . Because of the EMC customizations that need to be applied to the Vendors code it is not currently available. EMC will include this in our next release of Policy Manager, however we do NOT have a projected release date as to when that will occur.
In an ideal implementation of ESRS with the Gateway in the DMZ the Policy Manager would / should be located on a host on your production environment which would normally have access to the internet thus eliminate this problem. The Policy Manager is NOT internet facing and would only need ports 8090 and 8443 outbound from the Gateway in the DMZ to the Policy Manager DMZ. EMC has NO access to you Policy Manager. .
Doxx2
25 Posts
1
August 12th, 2014 11:00
There is currently no work around for this. The Vendor complied the current Policy Manager with dynamic libraries that cause the Policy manager to go to Adobe to retrieve them . We at EMC are aware of the problem and have escalated it to the vendor - and it is fixed in their current release generic release of Policy Manager . Because of the EMC customizations that need to be applied to the Vendors code it is not currently available. EMC will include this in our next release of Policy Manager, however we do NOT have a projected release date as to when that will occur.
In an ideal implementation of ESRS with the Gateway in the DMZ the Policy Manager would / should be located on a host on your production environment which would normally have access to the internet thus eliminate this problem. The Policy Manager is NOT internet facing and would only need ports 8090 and 8443 outbound from the Gateway in the DMZ to the Policy Manager DMZ. EMC has NO access to you Policy Manager. .