On Thu, Oct 9, 2014 at 8:49 AM, Sebastien Blanc <scm.blanc(a)gmail.com> wrote:
The interface design is not a big deal. Would be nice to add some
>> filtering to the search:
>>
>> - search by owner
>> - search by variant
>> - search by app name
>>
>
> regarding the search and filtering, I do see value in it, but - for
> timing reasons, let's please do that only once the other stuff is really
> in, and works.
>
> I don't expect a gazillion of PushApps on one server instance, so
> pagination of a few pages, sorted by "username" should be good enough
>
+1 , it's just a matter of adding "ORDER BY developer" and I think we can
reuse our pagination component from the installation page.
But indeed, for the next releases adding some filtering will be nice.
yep, we had that as a question for 1.0.0 earlier, but agreed to not add
search/filtering due to timing. I'd not like to change that on 1.0.x
-M
>
>
>>
>>
>> >
>> > That's just one initial thought. Once we agree on this overall
>> feature, I
>> > think we will nail the details of the 'how' in the relevant JIRA
>> subtasks
>> > of AGPUSH-697.
>> > However I fully agree that we need to apply some tweaks to the
>> existing UI,
>> > so that the owner name is visible when the 'admin' is looking at
the
>> > "application overview" page, like in the screenshot.
>>
>> Subtasks already created:
https://issues.jboss.org/browse/AGPUSH-697
>>
>>
>> >
>> >
>> > >
>> > > That's why I think the mininum for the UPS admin interface must be
>> > > defined, right
>> > > now, before start the whole implementation. What would you expect to
>> see
>> > > when you query the whole database?
>> > >
>> >
>> > I thought about adding 'pagination' on the "application
overview" page,
>> > similar like we do on the installations.
>> >
>> > -Matthias
>> >
>> >
>> >
>> > >
>> > > >
>> > > >
>> > > > >
>> > > > > >From my understanding, Keycloak will just manage these
users and
>> > > unless
>> > > > > something has changed, we provide the fine grained
authorization
>> model
>> > > on
>> > > > > UPS. Like
>> > > > > we did in the past.
>> > > > >
>> > > >
>> > > > yeah, the users live in Keycloak - we somehow differentiate on
the
>> > > > role/user if we do a "select all" or just those for the
specific
>> user
>> > > >
>> > > >
>> > > > >
>> > > > > Am I correct?
>> > > > >
>> > > > > [1] -
>> > >
http://lists.jboss.org/pipermail/keycloak-dev/2014-May/001851.html
>> > > > >
>> > > > > On 2014-10-08, Matthias Wessendorf wrote:
>> > > > > > Hi,
>> > > > > >
>> > > > > > as of today, we have a single user (admin), to revisit
that we
>> have
>> > > > > > AGPUSH-697 (see [1]).
>> > > > > >
>> > > > > > Based on changes over the months (e.g new UI and being
based on
>> > > > > Keycloak),
>> > > > > > I have updated our old spec/gist:
>> > > > > >
https://gist.github.com/matzew/ed0055000a8347488a37
>> > > > > >
>> > > > > > Greetings,
>> > > > > > Matthias
>> > > > > >
>> > > > > > [1]
https://issues.jboss.org/browse/AGPUSH-697
>> > > > > >
>> > > > > > --
>> > > > > > Matthias Wessendorf
>> > > > > >
>> > > > > > blog:
http://matthiaswessendorf.wordpress.com/
>> > > > > > sessions:
http://www.slideshare.net/mwessendorf
>> > > > > > twitter:
http://twitter.com/mwessendorf
>> > > > >
>> > > > > > _______________________________________________
>> > > > > > aerogear-dev mailing list
>> > > > > > aerogear-dev(a)lists.jboss.org
>> > > > > >
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> > > > >
>> > > > >
>> > > > > --
>> > > > >
>> > > > > abstractj
>> > > > > PGP: 0x84DC9914
>> > > > > _______________________________________________
>> > > > > aerogear-dev mailing list
>> > > > > aerogear-dev(a)lists.jboss.org
>> > > > >
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> > > > >
>> > > >
>> > > >
>> > > >
>> > > > --
>> > > > Matthias Wessendorf
>> > > >
>> > > > blog:
http://matthiaswessendorf.wordpress.com/
>> > > > sessions:
http://www.slideshare.net/mwessendorf
>> > > > twitter:
http://twitter.com/mwessendorf
>> > >
>> > > > _______________________________________________
>> > > > aerogear-dev mailing list
>> > > > aerogear-dev(a)lists.jboss.org
>> > > >
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> > >
>> > >
>> > > --
>> > >
>> > > abstractj
>> > > PGP: 0x84DC9914
>> > > _______________________________________________
>> > > aerogear-dev mailing list
>> > > aerogear-dev(a)lists.jboss.org
>> > >
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> > >
>> >
>> >
>> >
>> > --
>> > Matthias Wessendorf
>> >
>> > blog:
http://matthiaswessendorf.wordpress.com/
>> > sessions:
http://www.slideshare.net/mwessendorf
>> > twitter:
http://twitter.com/mwessendorf
>>
>> > _______________________________________________
>> > aerogear-dev mailing list
>> > aerogear-dev(a)lists.jboss.org
>> >
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>> --
>>
>> abstractj
>> PGP: 0x84DC9914
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog:
http://matthiaswessendorf.wordpress.com/
> sessions:
http://www.slideshare.net/mwessendorf
> twitter:
http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev