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:
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
>