Now, when creating Pax Web 8 pax-web-jetty-bundle (all-in-one Jetty), I'm
getting:
java.util.ServiceConfigurationError:
org.eclipse.jetty.security.Authenticator$Factory: Provider
org.eclipse.jetty.security.jaspi.JaspiAuthenticatorFactory not a subtype
at
Hi
pax-web-jetty before Pax Web 8 used jetty-all, which has dependency on
jetty-jaspic, which has dependency on javax.security.auth.message...
Let me check it.
regards
Grzegorz Grzybek
pt., 29 paź 2021 o 13:12 Paul Stanley
napisał(a):
> The Jetty issue:
The Jetty issue: https://github.com/eclipse/jetty.project/issues/6554
resulted in pull request:
https://github.com/eclipse/jetty.project/commit/4fd1a4ea4b7a989ea16f40ba7c49dc553ae2ace1
This removed the check for the realm being set, thus always creating a
default identity service, even when one
Hello
What's the problem with Jetty 9.4.44? I checked with Pax Web 8 without any
changes and I got:
[INFO] Results:
[INFO]
[WARNING] Tests run: 201, Failures: 0, Errors: 0, Skipped: 2
...
[INFO]
[INFO] --- maven-failsafe-plugin:2.22.2:verify (verify) @
pax-web-itest-jetty ---
[INFO]
Hi Paul
Yes I know but it could be optional. I think I have another option, I’m trying
it now.
Regards
JB
> Le 29 oct. 2021 à 11:44, Paul Stanley a
> écrit :
>
> Hi JB,
>
> Jetty 9.4.44 now attempts to create the default instance of the jaspi,
> even if it is not installed or used.
>
Hi JB,
Jetty 9.4.44 now attempts to create the default instance of the jaspi,
even if it is not installed or used.
I've included the geronimo-jaspi implementation alongside the geronimo
-jaspic_1.0_spec to address the issue.
Note that ordering is important as there is static code begin used to
Hi guys,
I detected that Jetty 9.4.44 update breaks the authentication layer.
I’m fixing that and I will cut Pax Web 7.3.20 to integrate in Karaf 4.3.4.
I will keep you posted, however, the plan is still to submit Karaf 4.3.4 to
vote during the week end.
Regards
JB
> Le 12 oct. 2021 à 14:43,
