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(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/apiman-user

What's not clear to me at this point is how to disable the local Keycloak. In the section you highlighted, I had used <subsystem xmlns="urn:jboss:domain:keycloak-server:1.1"> <auth-server name="main-auth-server"> <enabled>false</enabled> <web-context>auth</web-context> </auth-server> </subsystem> But this is what gives the "Unknown keycloak-server subsystem tag: auth-server" error. I'm not sure where to look up the documentation of this subsystem; it's not in the documentation of the JBoss adapter for Keycloak. Do I just remove the subsystem completely from the xml file in order to disable the server? On 1/25/16, 4:21 PM, "Eric Wittmann" <eric.wittmann(a)redhat.com&gt; wrote: > Sorry, I meant this is the new configuration: > > https://github.com/apiman/apiman/blob/master/distro/wildfly9/src/main/reso > urces/overlay/standalone/configuration/standalone-apiman.xml#L408-L410 > > They split the keycloak config into two separate subsystems. > > -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(XmlCon >> figurationPersister.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(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/apiman-user >>