Hi Vivek ! 
The KeyCloak jsut gave me some directions for the migration, I copy paste it here :

Make sure Keycloak 1.0.0.RC1 is not running and run:

 # bin/standalone.sh -Dkeycloak.migration.action=export -Dkeycloak.migration.provider=singleFile -Dkeycloak.migration.file=<ADD A NAME FOR THE EXPORT FILE>

Then you need to manually edit the exported file:

1. Rename "auditEnabled" to "eventsEnabled"
2. Rename "auditExpiration" to "eventsExpiration"
3. Rename "auditListeners" to "eventsListeners"
4. Under "master" realm to all applications that ends with "-realm" add roles "view-events" and "manage-events" (you don't need to specify an id)
5. To "admin" composite role in master realm add "view-events" and "manage-events"
6. For each additional realm to "realm-management" application add roles "view-events" and "manage-events"
7. To "realm-admin" composite role in other realms add "view-events" and "manage-events"

Steps 1-3 are required, otherwise the import will fail. If steps 4-7 are not done Keycloak will throw a NPE if you try to access events log through the admin console, you can also do these steps afterwards through the admin console. 

Before starting Keycloak 1.0.1.Final clear the database, then run:

 # bin/standalone.sh -Dkeycloak.migration.action=import -Dkeycloak.migration.provider=singleFile -Dkeycloak.migration.file=<PATH TO ABOVE EXPORT FILE>

Please let us know if that helps.

Sebi

On Mon, Oct 6, 2014 at 11:34 AM, Sebastien Blanc <scm.blanc@gmail.com> wrote:


On Mon, Oct 6, 2014 at 10:41 AM, Matthias Wessendorf <matzew@apache.org> wrote:
Hello Vivek,

looks like a database migration problem from our Keycloak SSO layer. I will follow up with them.

That said, sounds like we may also have some higher priority for an export of the device metadata (and perhaps apps/variants), to allow an import on newer versions
+1 and indeed maybe consider apps/variants as well

@vivek In the mean time, I will ping the Keycloak team to see if they have some kind of migration script available or tips.
  

-Matthias

On Mon, Oct 6, 2014 at 7:40 AM, Vivek Pandey <vivek.pandey@pinelabs.com> wrote:

UPS team,

 

I was trying to upgrade to UPS 1.0.0 to UPS 1.0.1. When I started jboss after upgrading the wars, I found following errors in log

 

11:00:06,999 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/auth]] (MSC service thread 1-4) Servlet /auth threw load() exception: java.lang.IllegalArgumentException: Can not set boolean field org.keycloak.models.jpa.entities.RealmEntity.eventsEnabled to null value

        at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:164) [rt.jar:1.7.0_51]

 

It seems that I missed some database migration script. Can you point me to that script?

 

Thanks,

Vivek



This message may contain privileged and confidential information and is solely for the use of intended recipient. The views expressed in this email are those of the sender and not of Pine Labs. The recipient should check this email and attachments for the presence of viruses / malwares etc. Pine Labs accepts no liability for any damage caused by any virus transmitted by this email. Pine Labs may monitor and record all emails.


_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev