Hi!
just wanted to ask if anyone has had any issues building
aerogear-android-todo? I think I must have missed something obvious here as
it does not build for me :(
The details can be found here [1]
Thanks,
/Daniel
[1] https://gist.github.com/3826704
Hi everyone,
Today I finally got https://issues.jboss.org/browse/AEROGEAR-437 done, which means that now we have AeroGear Controller integrated with PicketBox, Picketlink and Deltaspike. Aerogear Security is the "middle-man" responsible for deal with security frameworks and JAX-RS authorization responses, currently.
And our routes now can be role based like this https://github.com/aerogear/aerogear-controller-demo/blob/master/src/main...:
route()
.from("/delorean").roles("admin")
.on(RequestMethod.GET)
.to(Home.class).anotherPage();
It was deployed on OpenShift: http://controller-abstractj.rhcloud.com/aerogear-controller-demo/. If you wan't to test it and file some jiras to me, just configure your application like I did at our demo https://github.com/aerogear/aerogear-controller-demo/blob/master/pom.xml#L86 and go for it.
What's missing?
- HTTP authentication responses (High priority now, to handle responses to the client side)
- Better exception handling
- Expose timeout configuration
- PicketBoxLoadUser must be optional
- Role validation improvements
- Page redirection on error (Daniel have been working on it - https://issues.jboss.org/browse/AEROGEAR-426)
- Registration page
- Code refactoring as usual
- Make use of aerogear controller at our TODO app (eating our own dog food)
--
"The measure of a man is what he does with power" - Plato
-
@abstractj
-
Volenti Nihil Difficile
I just sent a PR for AEROGEAR-499.
https://github.com/aerogear/aerogear-js/pull/5
these tests only test the client side api.
There will probably be other tests needed once the api is finalized, example, the isAuthenticated issue Matthias found
Hi,
I noticed some interesting behavior with the 'isAuthenticated' function.
It returns TRUE even when the pipe is not authenticated, because a
wrong(or no) authenticator has been attached,
See:
https://gist.github.com/3812824
IMO it should return FALSE when no authenticator is attached. Even on
a 'pipe connection' where no auth is required, the
'isAuthenticated:false' would be still wrong, as the connection is not
authenticated - since not required...
Any thoughts ?
Of course, this brings up the question if there should be some
'callback' that is invoke when the 'pipe' receives a 401. To indicate
'wrong' (or no) auth provided.. ?!
-Matthias
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
