Meh, that's not very appealing. We're on somewhat of a deadline, and do
expect huge numbers of users. Iterating over all of them, simply to get
their count, isn't going to be a viable solution. I'd really like to avoid
local caching. Can I somehow convince you to not see this as a new feature,
but rather an improvement slash bugfix for a missing attribute exposure? :)
On 23 March 2016 at 16:35, Stian Thorgersen <sthorger(a)redhat.com> wrote:
First 2.x release is probably July/August.
Admin rest endpoints will be backwards compatible, but we are discussing
at some point to introduce a v2. In this case v1 would be kept for at least
a while.
The Java admin client library will be completely rewritten at some point.
On 23 Mar 2016 15:30, "Guus der Kinderen" <guus.der.kinderen(a)gmail.com>
wrote:
> Understood. Although out-of-scope of this question and
> I-hate-when-they-ask-me-for-my-projects: when it 2.x available? :)
>
> Also - we just started work on integration, based on 1.9 - will 2.0 be
> API compatible?
>
> - Guus
>
> On 23 March 2016 at 16:28, Stian Thorgersen <sthorger(a)redhat.com> wrote:
>
>> Thanks for the awesome comment.
>>
>> We're actually planning to add a count to our console, so this will be
>> added. Just wanted to point out that we're not adding more features to
>> 1.9.x at this point so this won't be available until 2.x.
>> On 23 Mar 2016 14:09, "Guus der Kinderen"
<guus.der.kinderen(a)gmail.com>
>> wrote:
>>
>>> Thanks for your fast response! I created
>>>
https://issues.jboss.org/browse/KEYCLOAK-2704 to track the
>>> getUsersCount() REST exposure.
>>>
>>> - Guus
>>>
>>> On 23 March 2016 at 14:52, Marek Posolda <mposolda(a)redhat.com> wrote:
>>>
>>>> On 23/03/16 10:30, Guus der Kinderen wrote:
>>>>
>>>> Hi there,
>>>>
>>>> Recently, I switched from WSO2 Identity Server to Keycloak, and all of
>>>> a sudden, the sun is shining a bit brighter, birds are singing cheerful
>>>> songs, and I'm pretty sure I just saw a unicorn pass by, leaving
>>>> multi-colored droppings. Thanks!
>>>>
>>>> Nice summary, we should put to our homepage :-)
>>>>
>>>>
>>>> That being said, I'm still pretty new, and could use some help.
I'll
>>>> probably have more questions like these pretty soon. Is there a instant
>>>> messaging based channel (IRC, XMPP?) where you guys hang out? For the
>>>> entry-level questions that I have, that might be more suitable.
>>>>
>>>> We have #keycloak on freenode, but using keycloak-user mailing list is
>>>> better as not all members are on IRC and asynchronous channel is
preferred.
>>>>
>>>>
>>>> In any case: my first question: We're using keycloak to form the
user
>>>> base of our existing product. Integration is going well, but I'm
running
>>>> into a snag: the existing product has a paged user overview - much like
the
>>>> keycloak administrative interface. However, unlike the keycloak
interface,
>>>> I need to be able to calculate the exact amount of pages (keycloak
resorts
>>>> to having a 'next page' button only, I need to explicitly
provide
>>>> references to every page).
>>>>
>>>> To be able to integrate, I need to find a way to retrieve the total
>>>> number of users for a particular realm. So far, I'm retrieving all
users to
>>>> be able to count them, which quite obviously defeats the purpose of
having
>>>> a paginated call in the first place. Is there a better way than
>>>> keycloak.realm( "myRealm" ).users().search( null, null, null
).size() ?
>>>>
>>>> We have model method for getUsersCount(), but looks we don't have it
>>>> exposed through admin REST endpoint. Feel free to create JIRA.
>>>>
>>>> Marek
>>>>
>>>>
>>>> Kind regards,
>>>>
>>>> Guus
>>>>
>>>>
>>>> _______________________________________________
>>>> keycloak-user mailing
listkeycloak-user@lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/keycloak-user
>>>>
>>>>
>>>>
>>>
>>> _______________________________________________
>>> keycloak-user mailing list
>>> keycloak-user(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/keycloak-user
>>>
>>
>