<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 29/06/16 11:43, <a class="moz-txt-link-abbreviated" href="mailto:us3r@mailbox.org">us3r@mailbox.org</a>
wrote:<br>
</div>
<blockquote
cite="mid:546128335.2813.1467193433328@office.mailbox.org"
type="cite">
<meta charset="UTF-8">
<p>We had the same (or a similar) problem that the versions were
4.0.0 and 4.0.5 and not considered compatible. As a hack you can
patch the version in MANIFEST.MF.</p>
<p>The documentation about the OSGi adapter is rather short
compared to other integrations. It basically says look in the
code. I consider it as undocument even though there is a section
in the ref guide because it tells you nothing.</p>
</blockquote>
The more detailed docs was added in latest release. See
<a class="moz-txt-link-freetext" href="https://keycloak.gitbooks.io/securing-client-applications-guide/content/topics/oidc/java/fuse-adapter.html">https://keycloak.gitbooks.io/securing-client-applications-guide/content/topics/oidc/java/fuse-adapter.html</a>
. But note that even in old release, there is bigger example with
extensive README (it's referenced from the official docs).<br>
<blockquote
cite="mid:546128335.2813.1467193433328@office.mailbox.org"
type="cite">
<p>The OSGi adapter would need more love. A major demotivator is
that this little plugin has CXF as a dependency (and we don't
use CXF in our application) and thus drags in dozens or hundreds
of other bundles that we don't really want to care about but
need some kind of setup which we couldn't get to work. I
understand that were are here in RedHat land and CXF is one of
their favourites but not mine. </p>
<p>We gave up on this and use the standalone security proxy. The
4.0.x version problem and the huge dependencies (CXF) show how
fragile this setup is. Even if you get it to work I'd guarantee
that it breaks quickly when you update some other bundles.
Version hell. <br>
</p>
</blockquote>
You can create JIRA for this issue and then we can possibly improve.
On the other hand, we focus mostly on JBoss Fuse rather than
standalone Apache Karaf (we just don't have possibility to test all
versions as each supported version adds some overhead etc) . And in
JBoss Fuse is Apache CXF already included, so it's not so big issue
in comparison to standalone karaf.<br>
<br>
Thanks,<br>
Marek<br>
<blockquote
cite="mid:546128335.2813.1467193433328@office.mailbox.org"
type="cite">
<p>us3r</p>
<blockquote type="cite">Ygor Castor <a class="moz-txt-link-rfc2396E" href="mailto:ygorcastor@gmail.com"><ygorcastor@gmail.com></a>
hat am 27. Juni 2016 um 13:09 geschrieben:<br>
<br>
<div dir="ltr">Done! Issue KEYCLOAK-3194.</div>
<br>
<div class="ox-5da4bda7df-gmail_quote">
<div dir="ltr">Em seg, 27 de jun de 2016 às 06:49, Marek
Posolda <<a moz-do-not-send="true"
href="mailto:mposolda@redhat.com">mposolda@redhat.com</a>>
escreveu:<br>
</div>
<blockquote>
<div>
<div>Hi, <br>
<br>
it looks the fuse/karaf adapter might be broken in
latest 2.0.0.CR1 release. Could you please create JIRA
for it? <br>
<br>
Thanks,<br>
Marek</div>
</div>
<div>
<div><br>
<br>
On 26/06/16 03:08, Ygor Castor wrote:<br>
</div>
</div>
<div>
<blockquote type="cite">
<div dir="ltr">I'm trying to install the keycloak
adapter at Karaf 4.0.5, but i'm running in some
problems, this one i'm not being able to solve: <br>
<br>
<div>karaf@root()> feature:install
keycloak-adapter-core</div>
<div>Error executing command: Unable to resolve root:
missing requirement [root] osgi.identity;
osgi.identity=keycloak-adapter-core;
type=karaf.feature; version="[2.0.0.CR1,2.0.0.CR1]";
filter:="(&(osgi.identity=keycloak-adapter-core)(type=karaf.feature)(version>=2.0.0.CR1)(version<=2.0.0.CR1))"
[caused by: Unable to resolve
keycloak-adapter-core/2.0.0.CR1: missing requirement
[keycloak-adapter-core/2.0.0.CR1] osgi.identity;
osgi.identity=org.keycloak.keycloak-adapter-core;
type=osgi.bundle; version="[2.0.0.CR1,2.0.0.CR1]";
resolution:=mandatory [caused by: Unable to resolve
org.keycloak.keycloak-adapter-core/2.0.0.CR1:
missing requirement
[org.keycloak.keycloak-adapter-core/2.0.0.CR1]
osgi.wiring.package;
filter:="(&(osgi.wiring.package=org.keycloak.authorization.client)(version>=2.0.0.CR1))"]]</div>
<div><br>
It seems that the feature can't find the
"org.keycloak.authorization" bundle, how can i fix
this?</div>
</div>
<br>
<br>
</blockquote>
</div>
<div>
<blockquote type="cite">
<pre>_______________________________________________
keycloak-user mailing list
<a moz-do-not-send="true" href="mailto:keycloak-user@lists.jboss.org" target="_blank">keycloak-user@lists.jboss.org</a>
<a moz-do-not-send="true" href="https://lists.jboss.org/mailman/listinfo/keycloak-user" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-user</a></pre>
</blockquote>
<br>
</div>
</blockquote>
</div>
_______________________________________________<br>
keycloak-user mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:keycloak-user@lists.jboss.org">keycloak-user@lists.jboss.org</a><br>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/keycloak-user">https://lists.jboss.org/mailman/listinfo/keycloak-user</a></blockquote>
</blockquote>
<br>
</body>
</html>