[aerogear-dev] Keycloak integration

Matthias Wessendorf matzew at apache.org
Tue May 6 07:31:52 EDT 2014


Let's see how the UPS integration goes, before we have too much KC
integration fields, ok ?
Once we got that done, I guess we have a good experience on proper
integration

-M


On Tue, May 6, 2014 at 1:04 PM, Matthias Wessendorf <matzew at apache.org>wrote:

> Yeah, sounds reasonable to me.
>
>
>
> On Tuesday, May 6, 2014, Corinne Krych <corinnekrych at gmail.com> wrote:
>
>> Good work!
>>
>> I wonder... It might be good to use the same integration for our OAuth2
>> server side demo in [1]
>> Here I used a KC server with realm.json configuration. Would it be
>> possible/worth it to replace all the configuration with plain Java?
>>
>> ++
>> Corinne.
>> [1]  https://github.com/aerogear/aerogear-integration-tests-server/pull/4
>>
>> On 06 May 2014, at 11:49, Matthias Wessendorf <matzew at apache.org> wrote:
>>
>> > Hello folks!
>> >
>> > Bill Burk was helping on the Keycloak front and besides fixing related
>> items on the Keycloak server, he also created an example that we can use as
>> a template for the actual integration. See [1]
>> >
>> > In the past, Bruno and I did integrate w/ an external Keycloak server
>> (see [2]), and we did include the keycloak.json file (See [3]). Thanks to
>> Bill's work on Keycloak, the 'protected app' no longer needs that, see [4].
>> > Also there is no more the need to customize the Keycloak Rest
>> Application (Stian and I did look into that as well).
>> >
>> >
>> > Good news: This means the UPS can stay as it is -> no need to change
>> internals (e.g. the 'bundle all in one WAR file' did force us to change our
>> '/rest' URLs, as Keycloak uses them, see [5]).
>> >
>> > Inside of our 'modular' Keycloak branch (see [2] again), we can apply
>> the work from Bill:
>> > * our current 'server' module will use a listener similar to [4]
>> > * create a "ups-auth" module similar to [6]
>> >
>> > On the 'ups-auth module' there is one area where we need to have some
>> future improvement:
>> > * testrealm.json -> needs to be in Java code, due to the URL being
>> hard-coded in there (we need to resolve the URL of the host, running the
>> bits). But, IMO for now that should be good enough.
>> >
>> > Bruno did offer to help out on the Keycloak integration, so that I can
>> go back to the analytics and mertrics feature. Thanks abstractj!! <3
>> >
>> > Greetings,
>> > Matthias
>> >
>> > [1]
>> https://github.com/keycloak/keycloak/tree/master/project-integrations/aerogear-ups
>> > [2]
>> https://github.com/aerogear/aerogear-unifiedpush-server/tree/keycloak-modular
>> > [3]
>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/keycloak-modular/server/src/main/webapp/WEB-INF/keycloak.json
>> > [4]
>> https://github.com/keycloak/keycloak/blob/master/project-integrations/aerogear-ups/app/src/main/java/org/keycloak/example/BootstrapListener.java
>> > [5]
>> https://github.com/aerogear/aerogear-unifiedpush-server/tree/keycloak-embedded
>> > [6]
>> https://github.com/keycloak/keycloak/tree/master/project-integrations/aerogear-ups/auth-server
>> >
>> >
>> > --
>> > 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
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> --
> Sent from Gmail Mobile
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140506/2d851f16/attachment-0001.html 


More information about the aerogear-dev mailing list