Securing the Polarion activation application

Beginning with version 2015, Polarion includes an activation application that makes it possible to install or update a license while the Polarion server is running, without the need to copy the license file manually to the target machine.

Warning:

Access to this application is not initially protected by user name and password

For production use it is highly recommended to secure access to this application directly in the Apache configuration.

Beginning with version 2015, there is a template Apache configuration file in the Polarion installation folder: \polarion\polarion\install\polarion.activation.conf.template

To ensure that a user name and password is requested when accessing the activation application (\polarion\activate\online and \polarion\activate\offline):

Copy this file to the Apache configuration folder, on Windows usually C:\Polarion\bundled\apache\conf\extra\.
Rename it to remove the .template extension.
Open the file in any text editor and modify it according to the instruction comments provided.
The template configuration is prepared for both user file authentication (like Polarion uses for Subversion by default, with user passwords data in a file) and for authentication against an LDAP server.

Note:

In a multi-instance setup with a coordinator plus one or more instances that can be clustered, it is necessary to use this configuration only on the coordinator server. The activation application runs only on the coordinator. For additional information about this type of setup, see Polarion ALM Enterprise Setup.

Securing the Polarion activation application

How do I

Learn more

Look up more details