<div dir="ltr">No specific reason it can't. Feel free to create a JIRA to request.<div><br>It's not something we can prioritize right now though. If you're willing to do a PR I can give you some pointers on how to implement it.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 23 November 2015 at 16:54, Erik Mulder <span dir="ltr"><<a href="mailto:erik.mulder@docdatapayments.com" target="_blank">erik.mulder@docdatapayments.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">We are extending KeyCloak with some custom functionality and we like to<br>
add an extra org.keycloak.provider.Spi and 'piggy-back' on the<br>
KeycloakSession.getProvider mechanism at various places. So we added a<br>
org.keycloak.provider.Spi file in the META-INF/services of our provider<br>
jar with the Spi implementation we made. But unfortunately, it's not<br>
picked up by the DefaultKeycloakSessionFactory, since the classloader<br>
that is used in ServiceLoader.load (DefaultKeycloakSessionFactory:56)<br>
doesn't have the custom provider jars in scope. Is this intentional?<br>
<br>
I can understand if you don't want some external Spi 'entering' the<br>
KeyCloak system. On the other hand, that's the 'own risk' of the<br>
developer creating it. We would like this constraint lifted if possible.<br>
If not, is there another way we can get our own Spi's added to the<br>
keycloak session without changing any KeyCloak sources? Like using a<br>
module instead of a 'plain' provider jar? Are these added modules in<br>
scope of the DefaultKeycloakSessionFactory classloader?<br>
<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" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-dev</a><br>
</blockquote></div><br></div>