<div dir="ltr">I thought with <span style="font-family:arial,sans-serif;font-size:13px">SPNEGO/</span><span style="font-family:arial,sans-serif;font-size:13px">Kerberos</span> we can achieve true SSO. Most large organisations are on a Windows environment and what these organisations want is once you authenticate to the corporate desktop, you should be able to then also access other applications without having to go through the login process. wonder how we can achieve this with KeyCloak?</div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Oct 12, 2014 at 2:29 AM, Bill Burke <span dir="ltr"><<a href="mailto:bburke@redhat.com" target="_blank">bburke@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Keycloak is an IDP server. It is not an adapter project for<br>
JBoss/Wildfly distributions. There's already a lot of great adapters to<br>
integrate your JBoss/Wildfly distributions to use SPNEGO and SAML. We<br>
already support federation with LDAP/AD for storage and authentication,<br>
OpenIDConnect and SAML as our auth protocols. The only thing on the<br>
roadmap for Kerberos is to make Keycloak to be a Kerberos to SAML/OpenID<br>
Connect bridge. It could be possible to poach or merge with Apache DS<br>
so that Keycloak could become a full Kerberos server too, but there are<br>
additional non-technical obstacles from us putting this option in our<br>
roadmap that I'd rather not discuss.<br>
<br>
But anyways, Keycloak doesn't use JAAS login modules on the IDP server<br>
side. On the client side doesn't make sense either as Keycloak only<br>
talks OpenIDConnect and SAML (in master).<br>
<br>
On 10/11/2014 11:10 AM, prab rrrr wrote:<br>
> Well, without support for external authentication, I am wondering how<br>
> big organizations that have already invested in Kerberos/SecurID etc,<br>
> would use this product? Typically, the Federation products like<br>
> Ping,OpenAM etc provide hooks for multiple stores to:<br>
> 1) Support Kerberos or SecureID or other authentication and retrieve the<br>
> user principal<br>
> 2) Retrieve user meta data from LDAP using that principal and<br>
> 3) Use the user meta data to customize the claims or userinfo.<br>
><br>
> I was hoping to see the above features in this product, given that<br>
> Keycloak already supports OpenID Connect (along with support for CORS,<br>
> javascript and future support for mobile devices) and it can act as an<br>
> Identity provider (OP). Perhaps Keycloak can synchronize all the user<br>
> information from stores like LDAP but it would still need a hook to plug<br>
> in external authentication<br>
><br>
> BTW I suggested realm to authetication mapping because different<br>
> applications in an organization have different authentication<br>
> requirements (some apps require SecuriID,some Kerberos etc) and those<br>
> applications can be mapped to the realm that uses an authentication<br>
> mechanism that they require.<br>
><br>
><br>
><br>
> On Saturday, October 11, 2014 10:29 AM, Bill Burke <<a href="mailto:bburke@redhat.com">bburke@redhat.com</a>><br>
<span class="">> wrote:<br>
><br>
><br>
> What you describe would work only if you treat Keycloak solely as an<br>
> identity store and wrote a login module that uses Keycloak admin<br>
> interface to obtain principal and role mapping information. Then there<br>
> is the issue of getting the Kerberos server and Keycloak using the same<br>
> user database. Then for this particular idea, you start to wonder if<br>
> using Keycloak is any benefit.<br>
><br>
> On 10/11/2014 9:54 AM, prab rrrr wrote:<br>
> > Wildfly makes a number of login modules available as a part of the<br>
> > Security sub system that include SPNEGO (see the link below). Since<br>
> > Keycloak supports defining new Realms, if you can provide some hooks to<br>
> > map the newly defined Realms to the Security sub system, I think it<br>
> > would address the issue. Picketlink examples shed some light on how it<br>
> > can be done.<br>
> ><br>
> ><br>
> <a href="https://docs.jboss.org/author/display/WFLY8/Security+subsystem+configuration" target="_blank">https://docs.jboss.org/author/display/WFLY8/Security+subsystem+configuration</a><br>
> ><br>
> ><br>
> > On Saturday, October 11, 2014 8:53 AM, Bill Burke <<a href="mailto:bburke@redhat.com">bburke@redhat.com</a><br>
</span><span class="">> <mailto:<a href="mailto:bburke@redhat.com">bburke@redhat.com</a>>> wrote:<br>
> ><br>
> ><br>
> > Kerberos is on our roadmap as there's some other Red Hat kerberos<br>
> > products we need to integrate wit. I don't understand Kerberos deep<br>
> > enough yet to know exactly what or how we would do it. My current<br>
> > thought that the Keycloak auth server would be a secured Kerberos<br>
> > service and become a bridge between kerberos and SAML or OpenID Connect.<br>
> ><br>
> > On 10/10/2014 5:24 PM, Raghuram wrote:<br>
> > > Can I put in an enhancement request for at least some hooks as I am<br>
> > not sure how a custom federation provider could be written for SPNEGO<br>
> > negotiation. This feature will be useful for all organizations that<br>
> > invested in Kerberos infrastructure.<br>
> > ><br>
> > >> On Oct 10, 2014, at 5:11 PM, Bill Burke <<a href="mailto:bburke@redhat.com">bburke@redhat.com</a><br>
> <mailto:<a href="mailto:bburke@redhat.com">bburke@redhat.com</a>><br>
</span><span class="">> > <mailto:<a href="mailto:bburke@redhat.com">bburke@redhat.com</a> <mailto:<a href="mailto:bburke@redhat.com">bburke@redhat.com</a>>>> wrote:<br>
> > >><br>
> > >> we don't support kerberos.<br>
> > >><br>
> > >>> On 10/10/2014 5:06 PM, Raghuram wrote:<br>
> > >>><br>
> > >>>> Has anyone tried out SPNEGO (Kerberos) authentication with key<br>
> cloak<br>
> > >>>> 1.0.2? If so, appreciate any input on how it can be achieved?<br>
> > >>><br>
> > >>> Sent from my iPhone<br>
> > >>><br>
> > >>><br>
> > >>> _______________________________________________<br>
> > >>> keycloak-user mailing list<br>
> > >>> <a href="mailto:keycloak-user@lists.jboss.org">keycloak-user@lists.jboss.org</a><br>
> <mailto:<a href="mailto:keycloak-user@lists.jboss.org">keycloak-user@lists.jboss.org</a>><br>
</span>> <mailto:<a href="mailto:keycloak-user@lists.jboss.org">keycloak-user@lists.jboss.org</a><br>
<span class="">> <mailto:<a href="mailto:keycloak-user@lists.jboss.org">keycloak-user@lists.jboss.org</a>>><br>
> > >>> <a href="https://lists.jboss.org/mailman/listinfo/keycloak-user" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-user</a><br>
> > >><br>
> > >> --<br>
> > >> Bill Burke<br>
> > >> JBoss, a division of Red Hat<br>
> > >> <a href="http://bill.burkecentral.com/" target="_blank">http://bill.burkecentral.com/</a><br>
> ><br>
> > >> _______________________________________________<br>
> > >> keycloak-user mailing list<br>
> > >> <a href="mailto:keycloak-user@lists.jboss.org">keycloak-user@lists.jboss.org</a><br>
> <mailto:<a href="mailto:keycloak-user@lists.jboss.org">keycloak-user@lists.jboss.org</a>><br>
</span>> <mailto:<a href="mailto:keycloak-user@lists.jboss.org">keycloak-user@lists.jboss.org</a><br>
<span class="">> <mailto:<a href="mailto:keycloak-user@lists.jboss.org">keycloak-user@lists.jboss.org</a>>><br>
> > >> <a href="https://lists.jboss.org/mailman/listinfo/keycloak-user" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-user</a><br>
> ><br>
> > --<br>
> > Bill Burke<br>
> > JBoss, a division of Red Hat<br>
> > <a href="http://bill.burkecentral.com/" target="_blank">http://bill.burkecentral.com/</a><br>
> ><br>
> ><br>
><br>
> --<br>
> Bill Burke<br>
> JBoss, a division of Red Hat<br>
</span>> <a href="http://bill.burkecentral.com" target="_blank">http://bill.burkecentral.com</a> <<a href="http://bill.burkecentral.com/" target="_blank">http://bill.burkecentral.com/</a>><br>
<div class="HOEnZb"><div class="h5">><br>
><br>
<br>
--<br>
Bill Burke<br>
JBoss, a division of Red Hat<br>
<a href="http://bill.burkecentral.com" target="_blank">http://bill.burkecentral.com</a><br>
_______________________________________________<br>
keycloak-user mailing list<br>
<a href="mailto:keycloak-user@lists.jboss.org">keycloak-user@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/keycloak-user" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-user</a><br>
</div></div></blockquote></div><br></div>