Hi Kunal, could you please tell me which version are you trying? I
would to try it locally here and see if I can reproduce the issue.
On Mon, Dec 14, 2015 at 2:16 PM, Kunal K <kunal(a)plivo.com> wrote:
Hi,
I'm using the migration script to import my users with a new hash algorithm
with the following command -
bin/standalone.sh -Dkeycloak.migration.action=import
-Dkeycloak.migration.provider=dir -Dkeycloak.migration.dir=keycloak-data
However all my salt values get changed mid way during the whole operation
and are stored (in the database) differently than what they should be. I
checked the code and saw that the script expects the salt values to be
base64 encoded. I tried encoding the salt to base64, but the same issue
persists.
Lastly I tried to update the salt in the database (postgres) directly using
an UPDATE statement, which worked well. Another observation I made is that
salt is a 'bytea' data type in postgres and is stored as a hex value.
Is there some issue with the import script? I'll be happy to fix it if
anyone points me in the right direction.
--
KUNAL KERKAR | PRODUCT ENGINEER
Plivo, Inc. 340 Pine St, San Francisco - 94104, USA
Web:
www.plivo.com | Twitter: @plivo, @tsudot
Free Incoming SMS for All US Short Codes – Get One Today!
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
--
- abstractj