Polarion Software Weblog

Automated migration of user permissions from version 2.6.5 (acls.xml) to version 3.0.0 (permissions.xml) can result in some users having more privileges than they had before the migration.

After the migration, an administrator should log in to the Administration perspective, go to the User Management : Permissions topic for the repository scope, and review and adjust user permissions. This should also be done for any projects which override the default configuration.

The main problematic part is if you changed something in the “GLOBAL SECURITY SETTINGS” section of acls.xml - due to the different logic behind permissions.xml the influence of this section is reduced when migrated to Polarion 3.0 as “GENERAL PERSISTENCE SECURITY SETTINGS” which only impacts entities like Work Items and not things like Administration.

Product Version: 3.0.0
Reported OS: Windows
Description:
A customer support ticket indicated Polarion ALM server was taking a very long time to start (over 3,800 seconds), and ran very slow afterwards. The cause was discovered to be the ZoneAlarm firewall. When the firewall was disabled by the customer, the problem persisted. However, When Polarion was installed on a computer with similar configuration but without ZoneAlarm firewall installed, startup and performance was normal.

Recommendations:
For the time being we recommend that you not attempt to run Polarion server on Windows computers having ZoneAlarm installed. We have not seen any problems with Polarion server running on Windows with the Windows firewall installed and activated, so we can suggest that as a firewall alternative.