Hi Stian,
Thanks for the response. Yes, I'm still seeing this issue with the very latest Github master (including today's commit #1038). This was working for me a couple of weeks ago, before more recent commits. We demoed the identity broker to our management using a PicketLink test idp.war (in same container) and also using MS WAAD on Azure. It's a key feature for us.
Let me provide more details about my environment:
- Building/running with Java 1.7
- Building master with 'mvn clean install -DskipTests=true -Pdistribution'
- Running within a JBoss EAP 6.1.0alpha container using the modules from distribution\as7-adapter-zip\target\unpacked in my ApplicationServer\modules\system\layers\base with the following differences:
- Had to add 'org/bouncycastle/main/bcprov-jdk16-1.46.jar' otherwise Keycloak complained on startup in server.log.
- Had to remove 'org/jboss/as' and 'org/jboss/aesh' as they were overwriting older JBoss EAP 6.1.0alpha versions and preventing startup.
- Deploying the auth-server.war by zipping the contents and renaming 'auth.war', placing in my standalone/deployments folder.
- Updating the standalone.xml file with the required Keycloak config. Defining the realm and secure deployments in that XML directly.
- Starting with a missing H2 datasource to ensure old data/schema is not the problem. On startup, I confirm admin's password and then re-build my DSIS realm.
Any help you can provide would be most appreciated. I'm using the Keycloak master as features being added now such as Kerberos/Spnego and Identity Brokering are critical use cases for our adoption.
Thanks,
Guy