[Apiman-user] Receiving HTML instead of JSON from Keycloak when trying to point apimanui to the API gateway

[Marc Savy]

To clarify - this is specifically referring to communication between the manager and the api gateway.

Glad to be of assistance!

On 15/12/2015 21:01, Paul Blair wrote:
> For the benefit of the list -- thanks to Marc and Eric's help, this issue
> was resolved.
>
> Currently the standalone.xml has to have enable-basic-auth set to true;
> i.e.,
>
> <kc:enable-basic-auth>true</kc:enable-basic-auth>
>
> -- no other auth mechanism is currently supported.
>
>
> On 12/15/15, 2:05 PM, "Marc Savy" <marc.savy at redhat.com> wrote:
>
> > I've just finished attempting to reproduce your situation - but
> > unfortunately (!) it works fine for me! All I needed to do was turn on
> > 'direct grants API' for apiman-gateway-api.
> >
> > Can you (suggest it to be off-list) send me your standalone.xml for
> > apiman, please? Feel free to anonymise as appropriate.
> >
> > On 15/12/2015 17:42, Paul Blair wrote:
> >> If I use the curl command you provided, I get a 302 with a redirect to
> >> Keycloak at /auth/realms/apiman/protocol/openid-connect/auth ... I
> >> changed
> >> the password for the apimanager user to make sure I was using the right
> >> password.
> >>
> >> If I hit that URI with a REST client, I get a "Login to apiman" HTML
> >> page
> >> back -- presumably it followed the redirect.
> >>
> >> I have a feeling Keycloak 1.7 may be expecting an additional parameter
> >> in
> >> the redirect URI. I wasn't seeing this when using 1.6.1.Final last week.
> >>
> >> On 12/15/15, 12:29 PM, "Marc Savy" <msavy at redhat.com> wrote:
> >>
> >>> /apiman-gateway-api/system/status/
> >>> <http://localhost:8080/apiman-gateway-api/system/status/>
> >>
> >
>
>
> _______________________________________________
> Apiman-user mailing list
> Apiman-user at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/apiman-user
>