[keycloak-dev] User Federation Provider Cache

Marek Posolda mposolda at redhat.com
Fri Jun 17 05:10:02 EDT 2016


On 16/06/16 16:38, Bill Burke wrote:
>>>> Sync users
>>>> --------------
>>>> We should still keep the option to sync users into Keycloak DB as we
>>>> have now. Note some persistent storages like LDAP are limited with
>>>> pagination. So the easiest possibility for some admins is just to sync
>>>> users, so they can easily search them in admin console.
>>>>
>>> Doing a full import just to support pagination is overkill. I'm
>>> guessing that a lot of deployments will not manage users through the
>>> Keycload admin console.  We can offer a manual a Sync SPI that
>>> providers can implement.
>> Maybe it's overkill for 90% of deployments, but remaining 10% want to
>> see all LDAP users in admin console immediatelly and hence want to sync
>> them? IMO it's always good to have SPI flexible so it can easily support
>> all the possible requirements. However I understand that it's not always
>> possible...
>>
>
> This is only an issue for large query result sets where you want to do 
> pagination.  IIRC, we couldn't figure out a way to do this in a 
> scalable manner without imports. 
yeah, I also can't see how to do pagination without imports, assuming 
the 3rd party store (ie. LDAP) doesn't have pagination support.

So then again, the question is if SPI should still have the option to 
support imports? Or maybe don't have it OOTB, but if customers start 
asking for pagination, we have the option to say them "ok, we will try 
to add it" instead of "no, you can't do that and there is no way to 
support it with current SPI" .

Marek


More information about the keycloak-dev mailing list