<div dir="ltr">Especially since this 'feature' requires new mock-ups (for the management section), some more time is really needed.<div><br></div><div>Moved the items to the next iteration</div><div><br></div><div>
-M</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Nov 7, 2013 at 2:36 PM, Matthias Wessendorf <span dir="ltr"><<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">There are still discussion going on, and the spec is also not ready, let;s move these items OUT of the nov. release:<div>
<br></div><div><a href="https://issues.jboss.org/browse/AGPUSH-351" target="_blank">https://issues.jboss.org/browse/AGPUSH-351</a> (spec)</div>
<div><a href="https://issues.jboss.org/browse/AGPUSH-282" target="_blank">https://issues.jboss.org/browse/AGPUSH-282</a> (impl)</div><div><br></div><div>-Matthias<br><div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Tue, Nov 5, 2013 at 4:09 PM, Matthias Wessendorf <span dir="ltr"><<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">What's the plan moving forward here ? <span><font color="#888888"><div>
<br></div></font></span><div><span><font color="#888888">-Matthias</font></span><div><div><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Oct 17, 2013 at 4:17 PM, Sebastien Blanc <span dir="ltr"><<a href="mailto:scm.blanc@gmail.com" target="_blank">scm.blanc@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Well, yes now that you said that :) Security based on Grouping.</div>
<div><div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Oct 17, 2013 at 4:15 PM, Matthias Wessendorf <span dir="ltr"><<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">you mean grouping ? </div><div><div><div class="gmail_extra">
<br><br><div class="gmail_quote">
On Thu, Oct 17, 2013 at 4:13 PM, Sebastien Blanc <span dir="ltr"><<a href="mailto:scm.blanc@gmail.com" target="_blank">scm.blanc@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">
<div>On Thu, Oct 17, 2013 at 3:44 PM, Matthias Wessendorf <span dir="ltr"><<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">any corp. org. may want some with just read-only access;<div>
The project lead is allowed to update the keys etc, but all the /normal/ developers can just see the IDs/secrets (so that they can use it in their server apps).</div>
</div></blockquote><div><br></div></div><div>This is also an interesting point, at some point don't we want the "read" rights limited to a single/set of pushapps or even a level deeper based on variants ? </div>
<div>Maybe in a big company, Bob the slacker intern has read access for his supracool push app but also has access to the Public Relation Push App keys ...</div><div><div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr">
<div><br></div><div>I guess that's not really (at least for me) closely related to a 'test via admin ui' feature</div><span><font color="#888888"><div><br></div><div>-M</div></font></span></div>
<div><div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Thu, Oct 17, 2013 at 3:39 PM, Corinne Krych <span dir="ltr"><<a href="mailto:corinnekrych@gmail.com" target="_blank">corinnekrych@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Not sure about the role: user.<br>
<br>
What will be the use case for this one?<br>
One use case, I see is if the 'user' is a tester. If we had the feature to send push notification test via admin UI (as we discussed in [1] and [2]).<br>
<br>
++<br>
Corinne<br>
[1] <a href="http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Push-Server-Admin-UI-td2678.html#a2718" target="_blank">http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Push-Server-Admin-UI-td2678.html#a2718</a><br>
[2] <a href="https://issues.jboss.org/browse/AGPUSH-38" target="_blank">https://issues.jboss.org/browse/AGPUSH-38</a><br>
<div><div><br>
On Oct 17, 2013, at 3:09 PM, Matthias Wessendorf <<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>> wrote:<br>
<br>
><br>
><br>
><br>
> On Thu, Oct 17, 2013 at 2:54 PM, Sebastien Blanc <<a href="mailto:scm.blanc@gmail.com" target="_blank">scm.blanc@gmail.com</a>> wrote:<br>
><br>
><br>
><br>
> On Thu, Oct 17, 2013 at 2:35 PM, Lucas Holmquist <<a href="mailto:lholmqui@redhat.com" target="_blank">lholmqui@redhat.com</a>> wrote:<br>
><br>
> On Oct 15, 2013, at 11:14 AM, Sebastien Blanc <<a href="mailto:scm.blanc@gmail.com" target="_blank">scm.blanc@gmail.com</a>> wrote:<br>
><br>
>> So for the next Unified Push Release (0.9) it would be nice if we could have some decent User Management, so I'm bumping this thread again.<br>
>> Some existing pointer :<br>
>><br>
>> - this thread :)<br>
>> - <a href="https://issues.jboss.org/browse/AGPUSH-351" target="_blank">https://issues.jboss.org/browse/AGPUSH-351</a><br>
>> - <a href="https://gist.github.com/sebastienblanc/6547605" target="_blank">https://gist.github.com/sebastienblanc/6547605</a><br>
>><br>
>> First point to define is :<br>
>> - What roles do we want ? And what can these Roles do ?<br>
><br>
> Admin - Can do all things including creating other users<br>
> Developer - can create apps and such. no access to the user management UI<br>
> User - read only - not sure if this one is needed<br>
> Yes, not sure also but why not ? Could be useful for a monitoring app/RHQ plugin that just want to retrieve the list of active pushapps ...<br>
><br>
><br>
> +1 - I like these three different roles, including their rights<br>
><br>
><br>
><br>
><br>
>> - How can these Roles be created (granted ...)<br>
>> - Design<br>
><br>
> I think we are still waiting on Hylke for this? not sure<br>
><br>
>><br>
>> Seb<br>
>><br>
>><br>
>><br>
>> On Tue, Sep 17, 2013 at 2:07 PM, Matthias Wessendorf <<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>> wrote:<br>
>><br>
>><br>
>><br>
>> On Tue, Sep 17, 2013 at 2:04 PM, Apostolos Emmanouilidis <<a href="mailto:aemmanou@redhat.com" target="_blank">aemmanou@redhat.com</a>> wrote:<br>
>> Following the discussion on GitHub [1], here are some points to be<br>
>> discussed about the user management flow:<br>
>><br>
>> - Does it make sense to add a role select field (admin, developer) on<br>
>> the enrollment page?<br>
>><br>
>> hrm, and (perhaps later) a section where to define the roles ? I think it's a good point, but not sure we need all this 'now' :-)<br>
>><br>
>> - Should we add an additional password field (password confirmation) on<br>
>> the enrollment page?<br>
>><br>
>> yeah, would be nice<br>
>><br>
>> - I think that the current logged in user shouldn't be available for<br>
>> deletion<br>
>><br>
>> yep, I agree<br>
>><br>
>> [1]:<br>
>> <a href="https://github.com/aerogear/aerogear-unifiedpush-server-admin-ui/pull/6" target="_blank">https://github.com/aerogear/aerogear-unifiedpush-server-admin-ui/pull/6</a><br>
>><br>
>><br>
>><br>
>> On Fri, 2013-09-13 at 10:15 +0200, Sebastien Blanc wrote:<br>
>> > A Jira has been created <a href="https://issues.jboss.org/browse/AGPUSH-351" target="_blank">https://issues.jboss.org/browse/AGPUSH-351</a><br>
>> > And draft structure has been created<br>
>> > here <a href="https://gist.github.com/sebastienblanc/6547605" target="_blank">https://gist.github.com/sebastienblanc/6547605</a> that can be used<br>
>> > as base for the Pull Request.<br>
>> ><br>
>> ><br>
>> > On Fri, Sep 13, 2013 at 5:53 AM, Douglas Campos <<a href="mailto:qmx@qmx.me" target="_blank">qmx@qmx.me</a>> wrote:<br>
>> > On Thu, Sep 12, 2013 at 09:39:28AM -0300, Bruno Oliveira<br>
>> > wrote:<br>
>> > > Would be nice to have a 8 hands document on it<br>
>> ><br>
>> ><br>
>> > who's going to start the pull request on it? it's SPECTIME!<br>
>> ><br>
>> > --<br>
>> > qmx<br>
>> > _______________________________________________<br>
>> > aerogear-dev mailing list<br>
>> > <a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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>
>> > aerogear-dev mailing list<br>
>> > <a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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>
>> aerogear-dev mailing list<br>
>> <a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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>
>> 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" target="_blank">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>
>> aerogear-dev mailing list<br>
>> <a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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>
> aerogear-dev mailing list<br>
> <a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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>
> aerogear-dev mailing list<br>
> <a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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>
> 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>
> aerogear-dev mailing list<br>
> <a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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>
</div></div><br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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></blockquote></div></div></div><br></div></div>
<br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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></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>
</div></div><br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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></blockquote></div><br><br clear="all"><span class="HOEnZb"><font color="#888888"><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>
</font></span></div></div></div></div></div><span class="HOEnZb"><font color="#888888">
</font></span></blockquote></div><span class="HOEnZb"><font color="#888888"><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>
</font></span></div></div></div></div>
<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></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>