

- #Password manager pro log4j update
- #Password manager pro log4j license
- #Password manager pro log4j mac
See the server/connect/doc/Protection_Connect_Administrator_Guide.doc for more information about it.Ībility to configure Protection! Connect™ connection.Ībility to post change notifications to Protection! Connect™.Ībility to export products to Protection! Connect™.Ībility to export license actions and customers to Protection! Connect™.
#Password manager pro log4j update
Note: If you are upgrading from earlier versions see: /server// folder for applicable database update scripts.Īdded Protection! Connect™ - a turnkey integration solution between Protection! Enterprise and third-party CRM and SFA applications.
#Password manager pro log4j mac
Improved algorithm for populating the "Activation Key" combo-box when adding Deactivation Action.Īdded ability to lock license to MAC address of the network card for FreeBSD and Linux on Intel x86-64 bit platform. Tracking of the "Usage Left Count" on Deactivation/Activation to preserve count value during move of the License to another computer. Protection! Enterprise Protection! Enterprise Server Fixed concurrency-related issues during Licenses generation.The following macro variables are currently supported:

Remove Bouncy Castle libraries from your application.Ībility to use macro variables in Product's Product Links. tUseBounc圜astleSecurityProvider(false)Ĭom.jp.圜astleSecurityProvider=falseģ. Instruct Protection! not to use Bouncy Castle either by: Use "RSA - SunJCE - 512" security algorithm for your product.Ģ. Native RSA cipher implementation on Java 6 with ability to remove dependency for Bouncy Castle Crypto API.ġ.To turn it ON either:Ĭom.jp.useJava6Context=true Note: all those reports require fresh activities to be collected.Ībility to eliminate the use of native libraries to obtain interface MAC address under Java 6 environment. They are in CSV format so they can be easily imported to Excel to make any further analysis. New metrics reports accessible via the "Licensing Statistics" dashboard: use "Download Reports" button.Updated the "Licensing Statistics" dashboard to offer persistent statistics data and better scope handling.


ACL | Lock License-Floating: acl_floating.xml ACL | Lock License-Named: acl_named.xml The following files can be updated on the fly: So any updates should be done within 1 min time range. Note, file locks will be automatically cleared after 1 min of timeout. Foe example, to update license users file ( licenseUsers.xml) a file must be created. Certainly, any lock files must be removed after complete of update. Such lock file should be named as a file to alter, adding. To prevent concurrent modification and possible data corruption you must first create an empty lock file.
