[Apiman-user] 1.2.1.Final / Wildfly 9 conflict with production deployment instructions
Eric Wittmann
eric.wittmann at redhat.com
Mon Jan 25 16:19:26 EST 2016
Oh poop.
You're right - they changed how KC is configured. Since we upgraded to
the latest keycloak, the production guide needs to change.
Here's the new configuration format:
https://github.com/apiman/apiman/blob/master/distro/wildfly9/src/main/resources/overlay/standalone/configuration/standalone-apiman.xml#L411-L442
I'll update the production guide and thanks for the notice.
-Eric
On 1/25/2016 3:50 PM, Paul Blair wrote:
> The production guide gives the following guidance about disabling the
> bundled Keycloak components:
>
> Because you will be using an external/standalone Keycloak server, it
> is useful to disable the Keycloak components that are bundled with
> the apiman quickstart. To do that, make the following modification
> to the *standalone-apiman.xml* file:
>
> <subsystemxmlns="urn:jboss:domain:keycloak:1.0">
> <auth-servername="main-auth-server">
> <enabled>false</enabled>
> <web-context>auth</web-context>
> </auth-server>
> </subsystem>
>
> When I start the server after upgrading from 1.2.0.Final, and comparing
> the standalone-apiman.xml config file with the old one, I get:
>
> 20:46:49,393 ERROR [org.jboss.as.server] (Controller Boot Thread)
> WFLYSRV0055: Caught exception during boot:
> org.jboss.as.controller.persistence.ConfigurationPersistenceException:
> WFLYCTL0085: Failed to parse configuration
> at
> org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:131)
> [wildfly-controller-1.0.2.Final.jar:1.0.2.Final]
> …
> Caused by: javax.xml.stream.XMLStreamException: Unknown
> keycloak-server subsystem tag: auth-server
>
>
> Any idea what this configuration should look like now?
>
>
> _______________________________________________
> Apiman-user mailing list
> Apiman-user at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/apiman-user
>
More information about the Apiman-user
mailing list