We tried the above fix on top of 1.7.0 by applying the changes from the
commits attached to the https://issues.jboss.org/browse/KEYCLOAK-2327
deployed, and it seems to have the same issue. If you have any
further update on this please let us know.
On Mon, Feb 1, 2016 at 4:02 PM, Stian Thorgersen <sthorger(a)redhat.com>
This could be related to
It's already fixed in master, so if you can try it out that would be
great. We should also have a 1.8.1.Final release this week with the fix in
On 30 January 2016 at 05:16, Malmi Samarasinghe <malmi.suh(a)gmail.com>
> Hi Bill,
> We are using keycloak 1.7.0 and rdbms (mysql)
> Malmi Samarasinghe
> On Jan 29, 2016 7:41 PM, "Bill Burke" <bburke(a)redhat.com> wrote:
>> Which version of keycloak? RDBMS or Mongo?
>> On 1/29/2016 12:35 AM, Malmi Samarasinghe wrote:
>> Hi Everyone,
>> In my application we create retrieve and assign role subsequently and it
>> seems that even for a small load (2-3 threads) with realm cache enabled
>> option, assign realm role call fails due to role not exist error and 404 is
>> returned from keycloak.
>> With the realm cache disabled option the load works fine.
>> Please get back to me if you have any information on any other option we
>> can follow to get this issue sorted or on what action the realm cache will
>> be persisted to DB.
>> keycloak-user mailing
>> Bill Burke
>> JBoss, a division of Red Hathttp://bill.burkecentral.com
>> keycloak-user mailing list
> keycloak-user mailing list