this is the best tutorial i found for running keycloak behind an apache2
proxy
On 17/11/2017 14:47, mj wrote:
Hi,
See a similar thread this week by me, subject "upgrade to 3.4 issue".
I edited the standalone.xml that came with 3.4 by hand, putting in the
changes we did. That made keycloak 3.4 start. Perhaps you can try that too.
However, we are running behind an apache2 proxy, and also that doesn't
work anymore as it did in the past.
It seems only minor, 3.3 -> 3.4, but actually it's quite a big upgrade...
MJ
On 11/17/2017 02:11 PM, mph(a)tecbakery.com wrote:
> Hi
>
> I tried to upgrade our installation from 3.3 to 3.4, following the guide
> at
http://www.keycloak.org/docs/latest/upgrading/index.html, and am
> receiving the following error on startup.
> Comparing both default standalone.xml I found that in 3.3 the
> urn:wildfly:elytron: was 1.2, in 3.4 it is 1.0...
>
> Any help is highly appreciated.
>
> Martin
>
> /opt/keycloak/keycloak-3.4.0# bin/standalone.sh
> -Djboss.socket.binding.port-offset=9100 -b 0.0.0.0
> =========================================================================
>
> JBoss Bootstrap Environment
>
> JBOSS_HOME: /opt/keycloak/keycloak-3.4.0
>
> JAVA: /usr/lib/jvm/java-8-oracle/bin/java
>
> JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M
> -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true
> -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
>
> =========================================================================
>
> 13:55:39,468 INFO [org.jboss.modules] (main) JBoss Modules version
> 1.6.0.Final
> 13:55:40,161 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.7.SP1
> 13:55:40,462 INFO [org.jboss.as] (MSC service thread 1-8) WFLYSRV0049:
> Keycloak 3.4.0.Final (WildFly Core 3.0.1.Final) starting
> 13:55:42,484 ERROR [org.jboss.as.controller] (Controller Boot Thread)
>
> OPVDX001: Validation error in standalone.xml
> -----------------------------------
> |
> | 322: </deployment-permissions>
> | 323: </subsystem>
> | 324: <subsystem xmlns="urn:wildfly:elytron:1.2"
> final-providers="combined-providers"
disallowed-providers="OracleUcrypto">
> | ^^^^ Unexpected element '{urn:wildfly:elytron:1.2}subsystem'
> |
> | 325: <providers>
> | 326: <aggregate-providers name="combined-providers">
> | 327: <providers name="elytron"/>
> |
> | The primary underlying error message was:
> | > ParseError at [row,col]:[324,9]
> | > Message: Unexpected element '{urn:wildfly:elytron:1.2}subsystem'
> |
> |-------------------------------------------------------------------------------
>
> 13:55:42,487 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:143)
> at org.jboss.as.server.ServerService.boot(ServerService.java:387)
> at
>
org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:370)
> at java.lang.Thread.run(Thread.java:748)
>
> 13:55:42,491 FATAL [org.jboss.as.server] (Controller Boot Thread)
> WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting.
> See previous messages for details.
>
> _______________________________________________
> keycloak-user mailing list
> keycloak-user(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/keycloak-user
>
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user