Hi Enrico.
Sorry about that - I think the production guide is a little out of date
now that we released apiman against WildFly 9 and Keycloak 1.7.0. I
tried updating the guide, but apparently my instructions are incorrect
or incomplete. That's what I get for doing it too quickly.
We'll have a look at the guide asap and fix it up. @msavy is going to
have a swing at it later (hopefully) today or tomorrow.
What I can tell you right off the bat is that the realm file is probably
not quite right (I think I forgot to update it for KC 1.7.0).
You could try manually configuring your KC realm, or just wait for us to
update some stuff (the guide and the realm file). :)
-Eric
On 1/27/2016 5:32 AM, enrico wrote:
Hi all and thanks for this awesome project,
I'm trying to setup an Apiman instance pointing to external Keycloak
server (and Elastic search, I don't know if it could be related)
but I'm not able to log in.
The Apiman version is 1.2.1.Final and Keycloak 1.8.0.CR3.
In standalone-apiman.xml I have removed the lines:
https://github.com/apiman/apiman/blob/master/distro/wildfly9/src/main/res...
and
https://github.com/apiman/apiman/blob/master/distro/wildfly9/src/main/res...
and set the auth server in
https://github.com/apiman/apiman/blob/master/distro/wildfly9/src/main/res...
The apiman-realm is taken from
https://raw.githubusercontent.com/apiman/apiman/master/distro/data/src/ma...
and I have substituted the "secret" fields with the values from
standalone-apiman.xml.
Relevant ERROR logs from Apiman
org.keycloak.adapters.OAuthRequestAuthenticator are:
failed to turn code into token
status from server: 400
{"error_description":"Client secret not provided in
request","error":"unauthorized_client"}
Any hint?
Cheers, Enrico
_______________________________________________
Apiman-user mailing list
Apiman-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/apiman-user