Hey guys,I've did some stabilizations inside the Bruno's keycloak.js branch and then rebased it against master.I've also shared this branch on aerogear/aerogear-unified-push-server repo, so we could all work on it:Dan, I believe this branch should fix issues you were seeing.~ LukasOn Tue, Jun 17, 2014 at 8:59 AM, Matthias Wessendorf <matzew@apache.org> wrote:
Bom Dia!On Tue, Jun 17, 2014 at 12:06 AM, Bruno Oliveira <bruno@abstractj.org> wrote:
Good morning peeps,
First I would like to thank Bill Burke, Stian, Sebastien and Lukas for dedicating
their time helping with Keycloak integration.Great to hear! :-)
I think we are almost done, this is the current branch:
https://github.com/abstractj/aerogear-unifiedpush-server/tree/keycloak.js. And now most
of issues were gone and is also possible to display the current logged
in user.
Now I'm working on fix the sender endpoint, to be more precise we need
to remove the HTTP basic authentication for sending push messages
now that most of the endpoints are protect by Keycloak.Is the reason here that the 'sending endpoint' is also accessed from the AdminUI, for the 'compose a push' feature?If it's really required I am OK with that. However, I'd prefer to avoid it, as changing the behaviour of one of our two HTTP_BASIC endpoints ('device registration' and 'sending') also requires changes/updates on the relevant client SDKs.
Greetings,MatthiasIf you try to
send a push message based on my branch you will see the basic
authentication form atm.
If you have a better idea, I'm all ears.
--
abstractj
_______________________________________________
aerogear-dev mailing list
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@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev