11:52 a.m.
Good morning my friends, decouple AeroGear from Keycloak was easy[1], we
did that last week. This week I'm struggling with auth server url which
must be dinamically replaced[2], for this reason I started a discusson
on keycloak-dev mailing list[3].
Based on the discussion there, I started some changes[4], moved most of
configuration be programatically[5] and make use of placeholders, as
well move our client-side configuration[6]. Altough I'm getting an annoying
exception[7]
and already reported to KC team (certainly something missing).
Some of the possible alternatives to KC placeholders:
1. During the configuration wizard, generate the JSON file and store in
some place. The problem is: Keycloak.js must be able to retrieve this
resource, otherwise, won't happen.
2. Allow people to upload their own configuration files to the server,
which requires to manually change it (I don't like it, but works).
If you're feeling bored and want to try my branch:
1. docker run -it -p 8080:8080 -p 9090:9090 jboss/keycloak
2. Login at http://dockerip:8080/auth
3. Add a real and upload ups-realm.json
4. git clone git@github.com:abstractj/aerogear-unifiedpush-server.git &&
switch to strawman branch
5. mvn clean install
6. Deploy ag-push to WildFly
7. Try it (an exception is expected like I mentioned)
I have switch to another task at the moment, and wanted to give to you a
heads up, just in case you want to try/help.
[1] -
https://github.com/abstractj/aerogear-unifiedpush-server/commit/e8fc8461f...
[2] -
https://github.com/abstractj/aerogear-unifiedpush-server/commit/e8fc8461f...
[3] - http://lists.jboss.org/pipermail/keycloak-dev/2014-November/003096.html
[4] -
https://github.com/abstractj/aerogear-unifiedpush-server/commit/d5298d613...
[5] -
https://github.com/abstractj/aerogear-unifiedpush-server/commit/d5298d613...
[6] -
https://github.com/abstractj/aerogear-unifiedpush-server/commit/d5298d613...
[7] - https://gist.github.com/abstractj/ef42e28903e470d5033d
--
abstractj
PGP: 0x84DC9914
11:56 a.m.
One more thing...
- bin/jboss-cli.sh
- connect
- /system-property=keycloak.url:add(value="http://authserverip:8080/auth")
On 2014-11-27, Bruno Oliveira wrote:
Good morning my friends, decouple AeroGear from Keycloak was easy[1],
we
did that last week. This week I'm struggling with auth server url which
must be dinamically replaced[2], for this reason I started a discusson
on keycloak-dev mailing list[3].
Based on the discussion there, I started some changes[4], moved most of
configuration be programatically[5] and make use of placeholders, as
well move our client-side configuration[6]. Altough I'm getting an annoying
exception[7]
and already reported to KC team (certainly something missing).
Some of the possible alternatives to KC placeholders:
1. During the configuration wizard, generate the JSON file and store in
some place. The problem is: Keycloak.js must be able to retrieve this
resource, otherwise, won't happen.
2. Allow people to upload their own configuration files to the server,
which requires to manually change it (I don't like it, but works).
If you're feeling bored and want to try my branch:
1. docker run -it -p 8080:8080 -p 9090:9090 jboss/keycloak
2. Login at http://dockerip:8080/auth
3. Add a real and upload ups-realm.json
4. git clone git@github.com:abstractj/aerogear-unifiedpush-server.git &&
switch to strawman branch
5. mvn clean install
6. Deploy ag-push to WildFly
7. Try it (an exception is expected like I mentioned)
I have switch to another task at the moment, and wanted to give to you a
heads up, just in case you want to try/help.
[1] -
https://github.com/abstractj/aerogear-unifiedpush-server/commit/e8fc8461f...
[2] -
https://github.com/abstractj/aerogear-unifiedpush-server/commit/e8fc8461f...
[3] - http://lists.jboss.org/pipermail/keycloak-dev/2014-November/003096.html
[4] -
https://github.com/abstractj/aerogear-unifiedpush-server/commit/d5298d613...
[5] -
https://github.com/abstractj/aerogear-unifiedpush-server/commit/d5298d613...
[6] -
https://github.com/abstractj/aerogear-unifiedpush-server/commit/d5298d613...
[7] - https://gist.github.com/abstractj/ef42e28903e470d5033d
--
abstractj
PGP: 0x84DC9914
--
abstractj
PGP: 0x84DC9914
9:58 a.m.
Hey Bruno, thanks for detailed instriuctions, the last comment saved me
some time. :-)
I have followed your instructions, except binding Keycloak to
localhost:10080 and deploying WildFly to localhost:8080.
I have configured keycloak.url appropriately, but then I get
http://localhost:8080/ag-push/:
Unable to resolve realm public key remotely, status = 404
I wonder, how you configured two wildfly instances, Keycloak's and UPS's to
avoid conflict?
As I said, I used Keycloak on another port, but that didn't seem to work.
~ Lukas
On Thu, Nov 27, 2014 at 6:56 PM, Bruno Oliveira <bruno(a)abstractj.org> wrote:
/system-property=keycloak.url:add(value="http://authserverip:8080/auth")
10:58 a.m.
Ahoy my friend, the keycloak instance is running here with docker at
10.0.1.7 and the other wildfly instance with UPS on localhost.
Does it make sense to you?
On 2014-11-28, Lukáš Fryč wrote:
Hey Bruno, thanks for detailed instriuctions, the last comment saved
me
some time. :-)
I have followed your instructions, except binding Keycloak to
localhost:10080 and deploying WildFly to localhost:8080.
I have configured keycloak.url appropriately, but then I get
http://localhost:8080/ag-push/:
Unable to resolve realm public key remotely, status = 404
I wonder, how you configured two wildfly instances, Keycloak's and UPS's to
avoid conflict?
As I said, I used Keycloak on another port, but that didn't seem to work.
~ Lukas
On Thu, Nov 27, 2014 at 6:56 PM, Bruno Oliveira <bruno(a)abstractj.org> wrote:
> /system-property=keycloak.url:add(value="http://authserverip:8080/auth")
>
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
abstractj
PGP: 0x84DC9914
11:33 a.m.
Yep, that make sense, I was accessing it through the port-forward bound to
localhost.
On Fri, Nov 28, 2014 at 5:58 PM, Bruno Oliveira <bruno(a)abstractj.org> wrote:
Ahoy my friend, the keycloak instance is running here with docker at
10.0.1.7 and the other wildfly instance with UPS on localhost.
Does it make sense to you?
On 2014-11-28, Lukáš Fryč wrote:
> Hey Bruno, thanks for detailed instriuctions, the last comment saved me
> some time. :-)
>
> I have followed your instructions, except binding Keycloak to
> localhost:10080 and deploying WildFly to localhost:8080.
> I have configured keycloak.url appropriately, but then I get
> http://localhost:8080/ag-push/:
>
> Unable to resolve realm public key remotely, status = 404
>
> I wonder, how you configured two wildfly instances, Keycloak's and UPS's
to
> avoid conflict?
> As I said, I used Keycloak on another port, but that didn't seem to work.
>
> ~ Lukas
>
>
> On Thu, Nov 27, 2014 at 6:56 PM, Bruno Oliveira <bruno(a)abstractj.org>
wrote:
>
> > /system-property=keycloak.url:add(value="http://authserverip:8080/auth
")
> >
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
abstractj
PGP: 0x84DC9914
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
9:44 a.m.
Hey man,
I gave it one more chance and this time I was able to make it work without
(almost) any hassle.
I just had to change app.js to redirect to correct keycloak instance:
https://github.com/lfryc/aerogear-unifiedpush-server/commit/3824e373b1164...
abstractj++
On Fri, Nov 28, 2014 at 6:33 PM, Lukáš Fryč <lukas.fryc(a)gmail.com> wrote:
Yep, that make sense, I was accessing it through the port-forward
bound to
localhost.
On Fri, Nov 28, 2014 at 5:58 PM, Bruno Oliveira <bruno(a)abstractj.org>
wrote:
> Ahoy my friend, the keycloak instance is running here with docker at
> 10.0.1.7 and the other wildfly instance with UPS on localhost.
>
> Does it make sense to you?
>
> On 2014-11-28, Lukáš Fryč wrote:
> > Hey Bruno, thanks for detailed instriuctions, the last comment saved me
> > some time. :-)
> >
> > I have followed your instructions, except binding Keycloak to
> > localhost:10080 and deploying WildFly to localhost:8080.
> > I have configured keycloak.url appropriately, but then I get
> > http://localhost:8080/ag-push/:
> >
> > Unable to resolve realm public key remotely, status = 404
> >
> > I wonder, how you configured two wildfly instances, Keycloak's and
> UPS's to
> > avoid conflict?
> > As I said, I used Keycloak on another port, but that didn't seem to
> work.
> >
> > ~ Lukas
> >
> >
> > On Thu, Nov 27, 2014 at 6:56 PM, Bruno Oliveira <bruno(a)abstractj.org>
> wrote:
> >
> > > /system-property=keycloak.url:add(value="
> http://authserverip:8080/auth")
> > >
>
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> --
>
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
12:08 p.m.
Lovely! I need more arms and brains to figure out how to dinamically
inform the remote URL for app.js.
Any idea is welcome.
On 2014-12-03, Lukáš Fryč wrote:
Hey man,
I gave it one more chance and this time I was able to make it work without
(almost) any hassle.
I just had to change app.js to redirect to correct keycloak instance:
https://github.com/lfryc/aerogear-unifiedpush-server/commit/3824e373b1164...
abstractj++
On Fri, Nov 28, 2014 at 6:33 PM, Lukáš Fryč <lukas.fryc(a)gmail.com> wrote:
> Yep, that make sense, I was accessing it through the port-forward bound to
> localhost.
>
> On Fri, Nov 28, 2014 at 5:58 PM, Bruno Oliveira <bruno(a)abstractj.org>
> wrote:
>
>> Ahoy my friend, the keycloak instance is running here with docker at
>> 10.0.1.7 and the other wildfly instance with UPS on localhost.
>>
>> Does it make sense to you?
>>
>> On 2014-11-28, Lukáš Fryč wrote:
>> > Hey Bruno, thanks for detailed instriuctions, the last comment saved me
>> > some time. :-)
>> >
>> > I have followed your instructions, except binding Keycloak to
>> > localhost:10080 and deploying WildFly to localhost:8080.
>> > I have configured keycloak.url appropriately, but then I get
>> > http://localhost:8080/ag-push/:
>> >
>> > Unable to resolve realm public key remotely, status = 404
>> >
>> > I wonder, how you configured two wildfly instances, Keycloak's and
>> UPS's to
>> > avoid conflict?
>> > As I said, I used Keycloak on another port, but that didn't seem to
>> work.
>> >
>> > ~ Lukas
>> >
>> >
>> > On Thu, Nov 27, 2014 at 6:56 PM, Bruno Oliveira
<bruno(a)abstractj.org>
>> wrote:
>> >
>> > > /system-property=keycloak.url:add(value="
>> http://authserverip:8080/auth")
>> > >
>>
>> > _______________________________________________
>> > aerogear-dev mailing list
>> > aerogear-dev(a)lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>> --
>>
>> abstractj
>> PGP: 0x84DC9914
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
abstractj
PGP: 0x84DC9914
3672
days inactive
3678
days old
6 comments
2 participants
participants (2)
-
Bruno Oliveira -
Lukáš Fryč