<div dir="ltr">Just a thought... regarding those two roles 'PushAdmin' and 'Super-User', IMO the Super-user should be able to see all apps (and their variants, including registered devices).<div><br></div><div>
<br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, May 21, 2014 at 2:55 PM, Bruno Oliveira <span dir="ltr"><<a href="mailto:bruno@abstractj.org" target="_blank">bruno@abstractj.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Thank you Matthias, I will look at it and return back with more<br>
questions if necessary.<br>
<div class="HOEnZb"><div class="h5"><br>
On 2014-05-21, Matthias Wessendorf wrote:<br>
> Hello,<br>
><br>
> yes - the handling is done by Keycloak itself; Last time we looked at user<br>
> management, we had the following in terms of roles:<br>
><br>
> <a href="https://gist.github.com/sebastienblanc/6547605" target="_blank">https://gist.github.com/sebastienblanc/6547605</a><br>
><br>
> Not sure the names of these roles are great.... let's see<br>
><br>
> Basically I think the role definition in the gist still addresses most of<br>
> what we want to archive:<br>
> * super-user: in charge of managing the UPS realm (including users); can<br>
> see _ALL_ push applications (that's the admin in Sebi's gist)<br>
> * PushAdmin: Someone that can manage applications and variants, but is not<br>
> able to add new users; he also sees only his applications/variants etc<br>
> (that's the developer in sebis gist)<br>
><br>
> The gist also contains a 'Viewer' role - At this point I am not sure we do<br>
> really need this. My impression is that if we have PushAdmins for our 1.0.0<br>
> community release that will be enough.<br>
><br>
> -Matthias<br>
><br>
><br>
><br>
><br>
> On Tue, May 20, 2014 at 10:02 PM, Bruno Oliveira <<a href="mailto:bruno@abstractj.org">bruno@abstractj.org</a>>wrote:<br>
><br>
> > Good morning peeps,<br>
> ><br>
> > Before I jump in <a href="https://issues.jboss.org/browse/AGPUSH-639" target="_blank">https://issues.jboss.org/browse/AGPUSH-639</a>. I would<br>
> > like to understand what do you guys want say with this issue.<br>
> ><br>
> > Currently Keycloak already has its own user/roles managements. What do<br>
> > you guys are looking for? Any specific requirements?<br>
> ><br>
> > --<br>
> ><br>
> > abstractj<br>
> > _______________________________________________<br>
> > aerogear-dev mailing list<br>
> > <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
> > <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
> ><br>
><br>
><br>
><br>
> --<br>
> Matthias Wessendorf<br>
><br>
> blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>
> sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
> twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a><br>
<br>
> _______________________________________________<br>
> aerogear-dev mailing list<br>
> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
<br>
<br>
--<br>
<br>
abstractj<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>
sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div>