Aha. So, we haven't done any testing whatsoever with KC 1.7. So we're not really
familiar with it (yet).
I think in our quickstarts (etc) we're actually still using 1.2.x.
That being said, if you hit (for instance) the status endpoint using `curl` do you have
any luck?
curl -v --user apimanager:apiman123!
http://localhost:8080/apiman-gateway-api/system/status/
Substitute auth info if needed.
I'm not sure what our adapters will do, given the large changes that have happened in
the intervening period.
----- Original Message -----
From: "Paul Blair" <pblair(a)clearme.com>
To: "Marc Savy" <marc.savy(a)redhat.com>
Cc: apiman-user(a)lists.jboss.org
Sent: Tuesday, 15 December, 2015 5:04:24 PM
Subject: Re: [Apiman-user] Receiving HTML instead of JSON from Keycloak when trying to
point apimanui to the API gateway
Looks like they must have changed this screen significantly with the
Keycloak 1.7.0.Final release:
http://tinypic.com/r/vy9shx/9
I am not wedded to Keycloak 1.7 -- should I go back to 1.6.1.Final?
On 12/15/15, 11:53 AM, "Marc Savy" <marc.savy(a)redhat.com> wrote:
No, at least in the version of KC I'm using, it is clients ->
"apiman-gateway-api" -> settings -> "Direct Grants Only"
http://i.imgur.com/1pDlEiQ.png
On 15/12/2015 16:46, Paul Blair wrote:
> I'm still seeing the same behavior.
>
> Under "Clients > Settings" in Keycloak I turned on "Direct Access
Grants
> Enabled" -- is that the setting you were referring to?
>
> I then tried also turning off "Standard Flow Enabled" and get back the
> error: "Client is not allowed to initiate browser login with given
> response_type. Standard flow is disabled for the client."
>
> I get the same errors using a REST client.
>
>
> On 12/15/15, 10:59 AM, "Marc Savy" <marc.savy(a)redhat.com> wrote:
>
>> apimanager
>
_______________________________________________
Apiman-user mailing list
Apiman-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/apiman-user