[Users] Fwd: Upgrading dwh and reports from 3.3.4 to 3.4.0?

[Gianluca Cecchi]

Previously I replied only to Yaniv.... see my progress below

---------- Forwarded message ----------
From: Gianluca Cecchi <gianluca.cecchi at gmail.com>
Date: Mon, Apr 7, 2014 at 10:14 PM
Subject: Re: [Users] Upgrading dwh and reports from 3.3.4 to 3.4.0?
To: Yaniv Dary <ydary at redhat.com>


On Mon, Apr 7, 2014 at 8:26 AM, Yaniv Dary <ydary at redhat.com> wrote:
> try to add:
> # ./js-export.sh --users --output-dir -DmasterPropsSource=/var/lib/ovirt-engine-reports/build-conf
>
>
> Yaniv


It didn't work with the same error as before...
Searching through as for some reason it wasn't able to find
jdbc.properties, I put myself into the directory containing it.
So that what it worked was this workflow:

[g.cecchi at tekkaman incoming]$ sudo su -

[root at tekkaman ~]# mkdir /tmp/js_export/

[root at tekkaman ~]# export
masterPropsSource=/var/lib/ovirt-engine-reports/build-conf

[root at tekkaman ~]# cd /var/lib/ovirt-engine-reports/build-conf

[root at tekkaman build-conf]#
/usr/share/jasperreports-server/buildomatic/js-export.sh --users
--output-dir /tmp/js_export
Using CE setup
First resource path:/usr/share/jasperreports-server/buildomatic/conf_source/ieCe/applicationContext-cascade.xml
Started to load resources
Resource name: applicationContext.xml
Resource name: applicationContext-cascade.xml
Resource name: applicationContext-data-snapshots.xml
Resource name: applicationContext-events-logging.xml
Resource name: applicationContext-export-config.xml
Resource name: applicationContext-export-import.xml
Resource name: applicationContext-logging.xml
Resource name: applicationContext-olap-connection.xml
Resource name: applicationContext-report-scheduling.xml
Resource name: applicationContext-search.xml
Resource name: applicationContext-security.xml
Resource name: applicationContext-themes.xml
Resource name: applicationContext-virtual-data-source.xml
Creating ActionModelService object.
Creating action model infrastructure.
Exporting user jasperadmin
Exporting user anonymousUser
Exporting user ovirt-admin
Exporting user admin

The problems is that I got the export done, but I now have the file
/tmp/js_export/users/ovirt-002dadmin.xml and it seems to have the
password in encrypted form too...

<?xml version="1.0" encoding="UTF-8"?>
<user>
    <username>ovirt-admin</username>
    <fullName>ovirt-admin</fullName>
    <password>ENC&lt;3DD74ECD56672B06967EBFC4E74A4394&gt;</password>
    <email></email>
    <externallyDefined>false</externallyDefined>
    <enabled>true</enabled>
    <role>ROLE_USER</role>
    <role>ROLE_ADMINISTRATOR</role>
</user>

So the question is how do I edit it or probably simply how to encrypt
the password....
Knowing how to encrypt, I probably could only generate the new
encrypted value and simply update the filed inside the jiuser table
(if it is the only table involved...)


But then I tried to modify the string
<password>ENC&lt;3DD74ECD56672B06967EBFC4E74A4394&gt;</password>

into
<password>mypassword</password>

and run the import

1) the command as suggested refused to update already existing users
[root at tekkaman build-conf]#
/usr/share/jasperreports-server/buildomatic/js-import.sh --input-dir
/tmp/js_export
Using CE setup
First resource path:/usr/share/jasperreports-server/buildomatic/conf_source/ieCe/applicationContext-cascade.xml
Started to load resources
Resource name: applicationContext.xml
Resource name: applicationContext-cascade.xml
Resource name: applicationContext-data-snapshots.xml
Resource name: applicationContext-events-logging.xml
Resource name: applicationContext-export-config.xml
Resource name: applicationContext-export-import.xml
Resource name: applicationContext-logging.xml
Resource name: applicationContext-olap-connection.xml
Resource name: applicationContext-report-scheduling.xml
Resource name: applicationContext-search.xml
Resource name: applicationContext-security.xml
Resource name: applicationContext-themes.xml
Resource name: applicationContext-virtual-data-source.xml
Creating ActionModelService object.
Creating action model infrastructure.
User jasperadmin already exists, skipping.
User anonymousUser already exists, skipping.
User ovirt-admin already exists, skipping.
User admin already exists, skipping.

2) So I ran this way with "--update" option:
[root at tekkaman build-conf]#
/usr/share/jasperreports-server/buildomatic/js-import.sh --update
--input-dir /tmp/js_export
Using CE setup
First resource path:/usr/share/jasperreports-server/buildomatic/conf_source/ieCe/applicationContext-cascade.xml
Started to load resources
Resource name: applicationContext.xml
Resource name: applicationContext-cascade.xml
Resource name: applicationContext-data-snapshots.xml
Resource name: applicationContext-events-logging.xml
Resource name: applicationContext-export-config.xml
Resource name: applicationContext-export-import.xml
Resource name: applicationContext-logging.xml
Resource name: applicationContext-olap-connection.xml
Resource name: applicationContext-report-scheduling.xml
Resource name: applicationContext-search.xml
Resource name: applicationContext-security.xml
Resource name: applicationContext-themes.xml
Resource name: applicationContext-virtual-data-source.xml
Creating ActionModelService object.
Creating action model infrastructure.
Updated user jasperadmin
Updated user anonymousUser
Updated user ovirt-admin
Updated user admin


And I see that in jiuser table actually it is automatically put the
encrypted value

In fact I'm able to access my Reports Portal with ovirt-admin user again.
Though I wasn't able to create a report that in some way could
demonstrate that previous data was retained after update from 3.3 to
3.4

Anyway I'm able to experiment again, even if this feature is all but
ready for production in my opinion

Gianluca