Accessing Alfresco Share via IVE portal

[animalfat]

With default rewriting behavior enabled for the portal, i was unable to view list of sites. After disabling rewrite for the share url, i can view sites and perform most functions, but the document library and calendar pages don't function properly – receive a permission denied error from the browser (lower left-hand corner). For example, no items display on the document library tab.

[mikeh]

What's an IVE portal?

Mike

[animalfat]

Instant Virtual Extranet, such as the one provided with our Juniper appliance. It is a hardware/software hybrid SSL virtual private network (VPN) appliance that offers users access to network resources securely, including web-enabled applications and email.

[animalfat]

Renenabled default rewrite behavior for policy. Implemented SSL configuration for share, which was absent. I can now access the document library index and calendar functions. However, I have noticed a couple javascript errors when clicking the site button (and other UI objects) the first time, behaves okay after initial attempt. Anyone else encounter these? How do I fix them?

Object doesn't support this property or method.

if(typeof(DanaDeferEval)!='undefined')DanaDeferEval
('false;');else top.DanaDeferEval('false;');

[mikeh]

That's not Alfresco code - I guess your portal must be injecting JavaScript that's clashing with ours somewhere.

Mike

[animalfat]

Yes, after more investigation I realize that the above excerpted code is a product of Juniper rewrite behavior. If I disable the default Juniper rewrite policy for the Alfresco Share url, I have the permission denied issue when attempting to access Document Library or Calendar.

I have configured SSL for tomcat and Alfresco as documented and explained elsewhere on the forum.

If I run with the default Juniper rewrite policy enabled, I can perform all the Alfresco functions and lookups, but I trip over the javascript errors.

I'm looking into upgrading the Juniper version, but this will require a lengthy testing effort, deployment, etc.

Does anyone know a different path to solving this issue?

Thanks.