And to be complete on the subject:
I's not possible to use jetty8's internal SecurityManager with cargo,
since even if jetty-policy.xml is loaded, the policy files directory
itself will still be liinked to the start.jar location.
I ended up switching to jetty9 under the standard J2EE SecurityManager.
On 06/16/2018 10:00 AM, Claude Brisson wrote:
Problem solved. I had to dig in cargo sources.
It's possible to override start.jar arguments with the
(undocumented!?) configuration property 'cargo.runtime.arg', so I was
able to enable Jetty 8 security policy module.
On 06/15/2018 06:23 PM, Claude Brisson wrote:
Hi.
I'm using cargo-maven2-plugin v1.6.8.
I'm trying to run a jetty container while enabling a security
manager, and I'm facing some problems:
- with the jetty8x container, Cargo cannot override jetty's
start.ini (since it's stored in the same place as start.jar) so I
don't know how to enable the provided jetty-policy.xml configuration
file
- with the jetty9x container, start.ini can know be customized by
Cargo but it seems that everything related to JDK security policies
has been dropped in this jetty release
Thanks for any suggestion.
Claude
_______________________________________________
jetty-users mailing list
[email protected]
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users
_______________________________________________
jetty-users mailing list
[email protected]
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users
_______________________________________________
jetty-users mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users
