Hi Scott,
Are you using the Karaf realm?
I'm not sure how the Jetty client is connected to the authentication store.
regards,
François
fpa...@apache.org
Le 20/06/2019 à 20:23, Leschke, Scott a écrit :
>
> I realize this isn’t strictly a Karaf question but I’m having trouble
> authenticating
By the way Ryan, I'm proposing to chat directly together to understand
your use case. Then we will send an update on the mailing list.
Just ping me directly.
Thanks !
Regards
JB
On 20/06/2019 18:41, Ryan Moquin wrote:
> In the second example, I'm referring to the repository with the feature
>
If you do feature:repo-add first with all repositories, sure it works.
The resolver doesn't install automatically required feature based on
req/cap: it validates the requirement is matched, so you have to install
the feature provided the cap. It allows you to "decoupled" the features
(without
In the second example, I'm referring to the repository with the feature
that has the capability though. I'm also referencing it from the test1
feature with a dependency=true attribute. If I verify the features with
the karaf-maven-plugin, I don't get any validation errors. I only do when
I
I realize this isn't strictly a Karaf question but I'm having trouble
authenticating using the Jetty client in Karaf 4.2.5. I'm getting a 401 from a
server (on a GET) that I'm unable to resolve even though I've verified that the
user/pwd I have is correct using both Chrome and Postman.
The
Hi Ryan,
it's what I thought: the cap/req are splitted in two repositories, where
each one doesn't know each other ;)
Here you have different options:
1. You can load all features repository in your Karaf distribution (in
etc/org.apache.karaf.features.cfg)
2. You can refer one repository in
Sure, I figured I would test with a simple example so I can make sure I'm
not doing anything stupid (I NEVER do anything stupid). If I created a
features xml like this:
--
http://karaf.apache.org/xmlns/features/v1.5.0;
