PowerFolder Server 8 SP2

Owned by Florian Lahr (Unlicensed)
Last updated: Dec 17, 2013

PowerFolder Server 8 Service Pack 2 Release Notes

Release date: September 2013

Build number: 8.2.44

(info) Client release notes can be found in the client documentation.

 

Important Notes about the PowerFolder Server 8 Service Pack 2 Release

AJP connector port

To support authentication through external sites like Shibboleth IdP portals, we now introduced an Apache JServ Protctol port, which can be enabled by a Server Configuration File setting:

ajp.port=8009

The port is not enabled by default, means if you want to use it, it has to be explicity added and set to the Server Configuration File. Separate documentation about how to use it together with Shibboleth and other external authentication systems will follow soon with the PowerFolder Server 9 release.

Improved startup script

There have been some bugfixes and improvements in the server startup script, therefore we recommend to replace the old PowerFolder-Server.sh file with the new one.

Please note to change the values for SERVER_INSTALL, SERVER_HOME and JAVA_MEM to match the values in the old file or your current environment.

Furthermore the PowerFolder-Server.pid file is now generated in the SERVER_HOME directory, not the SERVER_INSTALL, anymore. If you are using any init or monitoring script referencing the PID file, please adapt those change.

New setting for inviting external users

In the past it was not possible to control if existing users can invite new users, so they get an account on the server, without disabling the invitation function completely, except when using LDAP. Now we introduced a new Server Configuration File setting to disable external user invitations, when using the database only for user authentication:

server.invite.new_users.enabled

The setting is by default set to "true", means it is enabled, to not break existing installations. Therefore in most cases you don't need to change anything. Please also check the Permissions section in the Server Configuration File documentation

 

PowerFolder Server 8 Service Pack 2 Changelog

Improvements

  • AJP protocol support
  • Folder scanning improvements
  • Ha cluster node now shuts down instead of getting slow when running in a OutOfMemoryError situation
  • HA cluster performance improvements
  • Improved multi-hashing and salting of password in the database
  • Improved Shibboleth web login to get authenticated on the IdP portal first
  • Improvements to reduce the risk for config file corruption
  • MSSQL support
  • Option to force TLS encrypted connections to SMTP
  • Option to prevent invitation of users not existing in LDAP
  • Performance optimization while checking user quotas
  • Prevent folder creation if user does not have quota
  • Reduced unnecessary log output in cluster environments
  • Remove folders with no user or group members
  • Removed config parameter which stores removed folders in HA environments
  • Support for third LDAP server
  • Trial activation creates a new trial account automatically if account doesn't yet

Bugfixes

  • Admin is not able to pass owner permission to another user or himself
  • API enhancement to set folder owner as admin
  • Clicking on folders not backed up in the cloud leads to a 404 error
  • Creating a file sharing link on non-existant files shares the whole folder
  • Creating sub-directories or renaming files via web doesn't work properly
  • Database duplicate key errors
  • Duplicate accounts when inviting LDAP user before he logged in
  • Duplicate accounts when using different LDAP logon attributes
  • Files don't get deleted if the archiving process runs into a problem
  • Linux startup script creates a file called 2
  • OutOfMemory exception when running a HA cluster
  • Problems with datepicker and copy to clipboard when sharing via link
  • Remove folder if the folder is hosted on different server node
  • Script execution doesn't read stdout and stderr properly
  • Server startup script doesn't check if PID is actually running
  • Shibboleth users have the option to change their password
  • Transfer logging doesn't work
  • Upload considers storage quota of non-owner members
  • Web request problems in clustered environments
  • XSS security issue on login, activation and register page