Hi Frederick,
I'm sorry for the inconvenience caused by I introduced.
I created the JIRA ticket and I'll create the pull request soon.
https://issues.jboss.org/browse/KEYCLOAK-7984
Best regards,
--
Hiroyuki Wada
h2-wada(a)nri.co.jp
On 2018/08/02 10:45, Frederick Ding wrote:
For what it's worth, the solution that I just used was to set
the
priority manually on the database, with something like `UPDATE
required_action_provider SET priority = 10;` . That appears to have
worked around this migration bug.
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user