[keycloak-user] Keycloak issue 6115 workaround

Dominik Guhr pinguwien at gmail.com
Tue Feb 20 08:34:21 EST 2018


So, I tried it with unsynced and it seems to work (around ;) )

Thanks for the hint!

Am 19.02.18 um 15:16 schrieb Marek Posolda:
> Workaround can be to edit LDAP provider with edit mode UNSYNCED instead 
> of READ_ONLY. That way, you can change the locale (+ some other 
> properties), but those changes are written to DB, not to LDAP.
> 
> Also not sure if you use "import" mode or "no-import" mode. From quickly 
> looking at the code, it seems to me that with import mode, you can 
> change the locale and exception won't be thrown.
> 
> Marek
> 
> On 19/02/18 14:05, Dominik Guhr wrote:
>> Hi everyone,
>>
>> so I made a comment here:
>> https://issues.jboss.org/browse/KEYCLOAK-6115?_sscc=t explaining my
>> problem, which is, in short terms, the bug issued in 6115 (localization
>> with readonly ldap).
>> Would be very nice to get some help here for a workaround, for this
>> stops me to change the whole landscape to kc as authprovider.
>>
>> In short points:
>> - I don't want to build kc sources myself, for the root cause is issued
>> and will hopefully be worked on in near future
>> - I want to create a custom provider spi module which does exactly the
>> same than the "built-in", but want to apply the workaround(!) - catching
>> the readonlyexception when its thrown.
>> - This SPI seems not to have the same structure than the custom SPIs
>> which are described in the docs for extending server
>>
>> Any help would be highly appreciated!
>>
>> Best regards,
>> Dominik
>> _______________________________________________
>> keycloak-user mailing list
>> keycloak-user at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/keycloak-user
> 
> 


More information about the keycloak-user mailing list