[aerogear-dev] REST: auth: user registration endpoint

Douglas Campos qmx at qmx.me
Mon Jan 14 14:39:09 EST 2013


+1

On 14/01/2013, at 16:49, Matthias Wessendorf <matzew at apache.org> wrote:

> Hi,
> 
> our client libries are using the "auth/enroll" value for the actual
> registration request, examples:
> - https://github.com/aerogear/aerogear-ios/blob/master/AeroGear-iOS/AeroGear-iOS/security/AGAuthConfiguration.m#L40
> - https://github.com/aerogear/aerogear-js/blob/master/src/authentication/adapters/rest.js#L212
> - https://github.com/aerogear/aerogear-android/blob/master/src/org/jboss/aerogear/android/authentication/AuthenticationConfig.java#L29
> 
> However, the server uses a different default ("auth/register"):
> - https://github.com/aerogear/aerogear-security/blob/master/src/main/java/org/jboss/aerogear/security/rest/service/AuthenticationService.java#L48
> - https://github.com/aerogear/TODO/blob/master/server/src/main/java/org/aerogear/todo/server/security/rest/AuthenticationEndpoint.java#L51
> 
> It was a decision from the past, that we have this "model", however -
> rethinking causes some concerns... Is that really ideal? Wouldn't it
> be just
> better to have matching default, on the client AND the server ?
> 
> Please vote:
> [+1] let's change the server default to match the "enroll" setting
> from the client libraries
> [0] I don't care
> [-1] nah, let's keep all as is, since the client can override everything
> 
> 
> Cheers!
> Matthias
> 
> -- 
> Matthias Wessendorf
> 
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev




More information about the aerogear-dev mailing list