<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 02/10/15 08:49, Stian Thorgersen
wrote:<br>
</div>
<blockquote
cite="mid:CAJgngAfOHR8fU-yRPGE9YB+mpixdSrLiK6F1LUDdkhwji7FDTA@mail.gmail.com"
type="cite">
<div dir="ltr">We need to reorganize the modules soon. Things make
even less sense now.
<div><br>
</div>
<div>How about:</div>
<div><br>
</div>
<div>* keycloak-common - common classes re-used by both client
and server</div>
<div>* keycloak-client-api - client specific interfaces</div>
<div>* keycloak-server-api - server specific interfaces,
including spi and providers<br>
</div>
<div><br>
</div>
<div>Then we also would have:</div>
<div>* keycloak-json - common json classes (json
representations, jwt utils, etc.)</div>
<div>* keycloak-oidc - common OpenID Connect classes</div>
<div>* keycloak-saml - common SAML classes</div>
<div><br>
</div>
<div>Most SPI implementations would be moved into
keycloak-server, other than those that needs to be pluggable.
The SPI implementations that should be in separate modules
are:</div>
<div><br>
</div>
<div>* Mongo</div>
<div>* JPA - we can combine Liquibase and JPA into one</div>
<div>* Social providers</div>
<div>* Anything else?</div>
</div>
</blockquote>
LDAP and Kerberos federation providers? We don't want them to be
available in "minimal" distribution right?<br>
<br>
But I am not sure as Kerberos authenticator is available by default
in browser authenticationFlow (even if disabled by default). When
someone enables it and LDAP/Kerberos federation provider is not
available, it won't work.<br>
<br>
Marek<br>
<blockquote
cite="mid:CAJgngAfOHR8fU-yRPGE9YB+mpixdSrLiK6F1LUDdkhwji7FDTA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 1 October 2015 at 20:58, Bill Burke
<span dir="ltr"><<a moz-do-not-send="true"
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">The SAML
adapter had some dependencies on classes within
keycloak-core.<br>
Unfortunately though, keycloak-core brings in Jackson JSON
parser.<br>
So, I split out keycloak-core into keycloak-common and
keycloak-core.<br>
<br>
PR is pending, but it should be in when the Europeans wake
up.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Bill Burke<br>
JBoss, a division of Red Hat<br>
<a moz-do-not-send="true"
href="http://bill.burkecentral.com" rel="noreferrer"
target="_blank">http://bill.burkecentral.com</a><br>
_______________________________________________<br>
keycloak-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:keycloak-dev@lists.jboss.org">keycloak-dev@lists.jboss.org</a><br>
<a moz-do-not-send="true"
href="https://lists.jboss.org/mailman/listinfo/keycloak-dev"
rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-dev</a><br>
</font></span></blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
keycloak-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:keycloak-dev@lists.jboss.org">keycloak-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/keycloak-dev">https://lists.jboss.org/mailman/listinfo/keycloak-dev</a></pre>
</blockquote>
<br>
</body>
</html>