Hi,
My suggestion is upgrade to latest version of Keycloak. This issues was
already fixed.
The issue is all about role policies (and I think user policies too)
getting corrupted after exporting settings given that the policy is updated
in the database with the name of the role instead of its ID.
For login/password to access H2, check
${KEYCLOAK_HOME}/standalone/configuration/standalone.xml. There you will
find the datasource configuration used by Keycloak (KeycloakDS).
Regards.
On Fri, Nov 24, 2017 at 10:18 AM, Corentin Dupont <corentin.dupont(a)gmail.com
wrote:
I guys,
I encountered this bug:
https://issues.jboss.org/browse/KEYCLOAK-4340
Basically after exporting, my policies are inaccessible.
My keycloak version is 3.1.0.Final.
Is there a workaround?
Can I delete the policies via API?
Should I edit the database?
I connected to H2 database but there is no tables.
What is the login/password when logging to H2?
Cheers