[keycloak-dev] migration docs

Bill Burke bburke at redhat.com
Tue Feb 18 11:13:44 EST 2014

We discussed export before and I think its on the roadmap.  Export could 
only be done locally to the machine where the server is installed so 
only those that have access to the machine can get the export.  I was 
also thinking that when the export is initiated, the admin provides a 
password that would be used to encrypt the export.  The only thing I 
worry about is how long it would take to externalize to disk and encrypt.

On 2/18/2014 11:02 AM, Stian Thorgersen wrote:
> DB schema ;)
> For the future I though a simple way to update the DB would be to add an option to export the whole db to json. Then you just install a new fresh server, and import the db again. It's simpler than having to provide instructions on how to update the DB schema (which would be different for each db) and I don't think we can rely on Hibernates autoddl update feature for production dbs.
> ----- Original Message -----
>> From: "Bill Burke" <bburke at redhat.com>
>> To: keycloak-dev at lists.jboss.org
>> Sent: Tuesday, 18 February, 2014 3:57:15 PM
>> Subject: [keycloak-dev] migration docs
>> In the docbook, there is a MigrationFromOlderVersions.xml.  Please edit
>> this with things that may be different between alpha 1 and alpha2.
>> --
>> Bill Burke
>> JBoss, a division of Red Hat
>> http://bill.burkecentral.com
>> _______________________________________________
>> keycloak-dev mailing list
>> keycloak-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/keycloak-dev

Bill Burke
JBoss, a division of Red Hat

More information about the keycloak-dev mailing list