As the JIRA hints, you should be able to work around this issue by setting
up a cluster of two instances of Keycloak. In that case restarting one,
waiting for cluster to resync, then restart the other one should keep the
Initial Access Tokens alive.
You can upvote the JIRA to give it greater urgency.
On Thu, Feb 16, 2017 at 1:04 AM, andrew dwyer <andrewrdwyer(a)gmail.com>
wrote:
I’ve run into the issue of initial access tokens disappearing after
I
restart my standalone keycloak server. I’ve confirmed this issue still
occurs on the latest release (2.5.1.Final).
I can see that this issue has been logged previously (
https://issues.jboss.org/browse/KEYCLOAK-3708) but is still unresolved.
We’re keen to get this fixed and I’d like to help if I can. Can anyone
suggest why this occurs?
Thanks
Andrew Dwyer
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user