Details
Assignee
Ben HopkinsBen HopkinsReporter
Stuart FrenchStuart FrenchEdit Screen Preamble
<div class="notify info" style="margin-bottom: 10px;">
If you are a Pentaho customer, please use the <a href="http://support.pentaho.com">Customer Support portal</a> to log issues.
<p />
This system is used for logging bugs and enhancement requests only. Please use our <a href="https://community.pentaho.com">community at https://community.pentaho.com</a> if you have questions, configuration issues, or have an issue with a marketplace plugin as Pentaho does not support marketplace plugins unless written by Pentaho.
<p />
Lastly, when creating a bug, please provide as much detail as possible. To prevent unnecessary delays in reviewing your issue, please attach complete server logs, SQL/MDX logs where applicable, schemas, etc. Also, screen-shots and screen-cams are especially helpful in demonstrating the issue.
<p />
Thank-you so much,<br />
The Pentaho Team
</div>
Notice
<div class="notify info" style="margin-bottom: 10px;">
When an issue is open, the "Fix Version/s" field conveys a target, not necessarily a commitment. When an issue is closed, the "Fix Version/s" field conveys the version that the issue was fixed in.
</div>
Story Points
0Components
Affects versions
Priority
Unknown
Details
Details
Assignee
Reporter
Edit Screen Preamble
<div class="notify info" style="margin-bottom: 10px;">
If you are a Pentaho customer, please use the <a href="http://support.pentaho.com">Customer Support portal</a> to log issues.
<p />
This system is used for logging bugs and enhancement requests only. Please use our <a href="https://community.pentaho.com">community at https://community.pentaho.com</a> if you have questions, configuration issues, or have an issue with a marketplace plugin as Pentaho does not support marketplace plugins unless written by Pentaho.
<p />
Lastly, when creating a bug, please provide as much detail as possible. To prevent unnecessary delays in reviewing your issue, please attach complete server logs, SQL/MDX logs where applicable, schemas, etc. Also, screen-shots and screen-cams are especially helpful in demonstrating the issue.
<p />
Thank-you so much,<br />
The Pentaho Team
</div>
Notice
<div class="notify info" style="margin-bottom: 10px;">
When an issue is open, the "Fix Version/s" field conveys a target, not necessarily a commitment. When an issue is closed, the "Fix Version/s" field conveys the version that the issue was fixed in.
</div>
Story Points
Components
Affects versions
Priority
Unknown
It is physically possible to copy the .installed-licenses.xml file from one Pentaho installation to another to transfer all registered licenses.
Furthermore copying the whole Pentaho folder to a new machine also works as in: on the new machine the copied Pentaho runs properly and retains all licenses.
There are no options to automatically prevent this. There is no other documented way to prevent copying the file from one Pentaho system to another. So, customers need to manage licenses themselves, bearing in mind how many core licenses have been purchased.
The requirement is to have a feature which automatically prevents .installed-licenses.xml from being copied/used on different Pentaho installations.
We are asking for this so that we don't have to manually 'police' the distribution of the licenses on our different systems.
Business case details:
we (re)sell Pentaho as base of our data integration product to our customers. In that context the installations usually take place on IT systems provided by the customer, which we can access to perform all necessary steps for the installation. The customer's IT department retains full control of the system though, and therefore could just duplicate the installation for example to a different factory without us knowing. This is what we would like to prevent.