<div dir="ltr">Hi Stian,<div><br></div><div>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.</div><div><br></div><div>Let me provide more details about my environment:</div><div><ol><li>Building/running with Java 1.7</li><li>Building master with 'mvn clean install -DskipTests=true -Pdistribution'</li><li>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:</li><ol><li>Had to add 'org/bouncycastle/main/bcprov-jdk16-1.46.jar' otherwise Keycloak complained on startup in server.log.</li><li>Had to remove 'org/jboss/as' and 'org/jboss/aesh' as they were overwriting older JBoss EAP 6.1.0alpha versions and preventing startup.</li></ol><li>Deploying the auth-server.war by zipping the contents and renaming 'auth.war', placing in my standalone/deployments folder. </li><li>Updating the standalone.xml file with the required Keycloak config. Defining the realm and secure deployments in that XML directly.</li><li>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.</li></ol><div>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.</div></div><div><br></div><div>Thanks,</div><div>Guy</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Mar 12, 2015 at 3:49 AM, Stian Thorgersen <span dir="ltr"><<a href="mailto:stian@redhat.com" target="_blank">stian@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Are you still having issues or did you figure it out?<br>
<span class=""><br>
----- Original Message -----<br>
> From: "Guy Davis" <<a href="mailto:guydavis.ca@gmail.com">guydavis.ca@gmail.com</a>><br>
> To: <a href="mailto:keycloak-dev@lists.jboss.org">keycloak-dev@lists.jboss.org</a><br>
> Sent: Wednesday, 4 March, 2015 1:10:52 AM<br>
> Subject: [keycloak-dev] Issue with latest Github master and SAML IDP providers?<br>
><br>
> Good day,<br>
><br>
> I've been using a sample Picketlink IDP locally for testing the SAML v2.0 ID<br>
> brokering, however after updating to latest master and re-deploying<br>
> components, I'm getting the following error. Any tips?<br>
><br>
><br>
><br>
</span>> Thanks in advance,<br>
> Guy<br>
><br>
> _______________________________________________<br>
> keycloak-dev mailing list<br>
> <a href="mailto:keycloak-dev@lists.jboss.org">keycloak-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/keycloak-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-dev</a><br>
</blockquote></div><br></div>