<div dir="ltr">+1 Less maintenance sounds good to me.</div><div class="gmail_extra"><br><br><div class="gmail_quote">On 22 July 2014 11:00, 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"><br><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div class="h5">On Tue, Jul 22, 2014 at 10:58 AM, 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi All ! <div><br></div><div>I'm currently working on APGUSH-810[1] which consist in removing the dependency we still had on the deprecated aerogear-security project (RIP my friend).</div>
<div><br></div>
<div>But now, if I want to keep AeroDoc, feature equal as before, I have to add a LOT of code around security (to handle role, annotations etc ...). </div><div>AeroDoc is already quite complex and time consuming to maintain and the core scope is not security but advanced Push.</div>
<div><br></div><div>So ... What I would like to propose is to keep only the authentification (log in) and remove all the role handling part to simplify it.</div><div><br></div><div>The only effect that this will introduce, is that a logged in user can also access the admin to create leads.</div>
</div></blockquote><div><br></div></div></div><div>that is fine w/ me </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=""><div dir="ltr">
<div><br></div><div><br></div><div>Wdyt ? </div><div><br></div><div>Sebi</div><div><br></div><div><br></div><div>[1] <a href="https://issues.jboss.org/browse/AGPUSH-810" target="_blank">https://issues.jboss.org/browse/AGPUSH-810</a></div>
</div>
<br></div>_______________________________________________<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><span class="HOEnZb"><font color="#888888"><br></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>
<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></div>