Got it, I'll take a look and see what we can do.
Of the top of my head, I'd convert it to a servlet filter, I'll make
sure to file jiras and keep you posted.
Matthias Wessendorf wrote:
On Wed, Jun 26, 2013 at 8:55 PM, Bruno Oliveira <bruno(a)abstractj.org
<mailto:bruno@abstractj.org>> wrote:
Are we skipping PL now?
https://github.com/aerogear/aerogear-unified-push-server/blob/227ca43c6a4...
I'm asking, because the PL have already implemented it.
I did it for a few reasons. I thought about using some "extension" of
the PL Agent (or a wrapper): Something like "MobileVariantAgent.java"
That would have a variantID (similar to the login name) and a secret,
stored as an attribute.
Right now, what I really do is user the variantID and the secret and
check if a) variant does exist and master password matches.
For the PicketLink I am also a bit unsure if that here (stealing the
session) is bad:
https://issues.jboss.org/browse/PLINK-204
so, I could "login" for variant "123" and have the chance to add
"devices" for a different variant 122 (if that exists in the database).
I am very open, to go with the default filter from PL, but the above was
my motivation of doing what I did for:
* Sender endpoint
* MobileVariantInstance endpoint
-Matthias
--
abstractj
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org <mailto:aerogear-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Matthias Wessendorf
blog:
http://matthiaswessendorf.wordpress.com/
sessions:
http://www.slideshare.net/mwessendorf
twitter:
http://twitter.com/mwessendorf
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev