<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jun 19, 2013 at 11:55 AM, 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">Correct, our friend AeroGearUser became a zombie and no more belongs to<br>
our ecosystem.<br></blockquote><div><br></div><div><br></div><div style>which is good :) </div><div style> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
If someone is concerned about: username, loginName, whaTeVerName. It<br>
must be coordinated between server and client.<br></blockquote><div><br></div><div><br></div><div>+1 </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Possible solutions:<br>
<br>
- Accept 'username' as pretty name on the endpoint and make use of DTOs<br>
(I don't like)<br>
- Accept flexible names on client APIs +1<br></blockquote><div><br></div><div style>yeah. see AGIOS-35 for example (similar to what JS does)</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
- Extend SimpleUser from PL (I don't like it)<br>
<br>
Bear in mind that every security framework will have their own<br>
implementation and AeroGear security doesn't have control over it.<br></blockquote><div><br></div><div><br></div><div style>correct, that's why I prefer a flexible client API, like JS already has.</div><div style>
<br></div><div style><br></div><div style><br></div><div style><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im HOEnZb"><br>
Matthias Wessendorf wrote:<br>
> The PushServer is based on AeroGear security 1.0.1, and AeroGearUser is<br>
> gone in there.<br>
> With the 1.0.1 + PL The "underlying" PL User uses "loginName".<br>
> With AeroGear-Sec 1.0.0 we had the AeroGear User, which used "username".<br>
><br>
> That's the entire explanation :)<br>
><br>
><br>
> Coming back to the point of "configuration", that's needed on Android<br>
> and iOS (like the JS bits) for the matter of the "user" in AeroGear-Shiro<br>
> is using "username" as well, while the PL "User" has "loginName".<br>
<br>
</div><span class="HOEnZb"><font color="#888888">--<br>
abstractj<br>
</font></span><div class="HOEnZb"><div class="h5"><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></div>