Thanks Sergiy, I will review.
Regards
JB
On 11/28/2016 03:03 PM, Sergiy Shyrkov wrote:
Hello guys,
we've finally tested the fix successfully on our side and have submitted
it as a pull request: https://github.com/apache/karaf/pull/271
Thank you!
Kind regards
Sergiy
On Thu, 20 Oct 2016
Hello guys,
we've finally tested the fix successfully on our side and have submitted
it as a pull request: https://github.com/apache/karaf/pull/271
Thank you!
Kind regards
Sergiy
On Thu, 20 Oct 2016 08:59:03 +0200, Benjamin Papez
wrote:
Hi JB,
thanks for
Hi JB,
thanks for looking into it. I already created a jira:
https://issues.apache.org/jira/browse/KARAF-4784
The workaround with an own login module ain't that easy, because we do
not know the names of all current jaas configurations customers have
today (can be multiple per installation).
Hi Benjamin,
your proposal makes sense. I will review, create a Jira, and implement.
In the mean time, as a workaround, I think you can provide your own
login module acting as a bypass.
Regards
JB
On 10/18/2016 06:19 PM, Benjamin Papez wrote:
Hello,
we plan to use Karaf embedded in the
Hello,
we plan to use Karaf embedded in the next version of our Web
Application, which means that we still start the application server
(Tomcat/JBoss/Websphere). Some of our customers are using a JAAS
configuration, mainly Kerberos for SPNEGO. Unfortunately with the step
to use Karaf the