Re: [jetty-users] Different passwords for key store and trust store -- i

[Simone Bordet <sbordet@xxxxxxxxxxx>]

Hi,

On Tue, Nov 28, 2017 at 4:20 PM, Shawn Heisey <eclipse@xxxxxxxxxxxx> wrote:
> I may have uncovered a wrinkle here.  They have the key store and the trust
> store in the same file.  The info I have found says that each individual
> item in a JKS store can have its own password

We don't use that.

> ... but I wonder if maybe
> Jetty is mapping passwords to filenames, so that the password gets set when
> one variable is gathered, and then changed when the the other variable is
> gathered, which makes one of them fail.  Am I on the right or the wrong
> track here?

Jetty is not mapping passwords to filenames.
All Jetty does is to forward the configuration properties to the JDK
APIs, which (to my knowledge) also don't map passwords to files.

> This is something we are aware of.  The 9.4.0 release was December 2016, but
> I'm reasonably certain that the last time anyone looked closely at a major
> upgrade of Jetty was during the preparation for Lucene/Solr 5.0, which was a
> new major version for us.  That release was announced in February 2015.  I
> did look at upgrading Jetty to a 9.4.x version, but there were enough
> changes that Solr wouldn't compile -- methods were missing, and it wasn't
> immediately clear to me how to change the code. My upgrade attempt was long
> enough ago that I no longer remember exactly what the problems were.

File an issue to the Jetty issue tracking and we'll help you out :)
I don't think there is a lot of differences between 9.3.x and 9.4.x,
so it should be fairly easy to move to 9.4.x.

-- 
Simone Bordet
----
http://cometd.org
http://webtide.com
Developer advice, training, services and support
from the Jetty & CometD experts.