I did some work on this over the weekend. Maintaining backwards compatibility is going to be challenging due to the http connection pool being static. Since the http client now needs to be specific to a repository or destination, i'm not sure if that configuration will still work. Anyhow, i ended up down a rat role of trying to understand why some of the unit tests were failing and making it worse in the process.
On Wed, May 6, 2020 at 6:38 AM Michael Osipov <[email protected]> wrote: > Am 2020-05-05 um 22:03 schrieb Alex O'Ree: > > I was looking over the docs for the settings.xml file and noted that it > > looks like it's possible to access a nexus repository using a client > > certificate of sorts. It's not clear the docs if a JKS can be used or if > it > > must be a ssh private key or what. > > > > http://maven.apache.org/settings.html#servers > > > > I wanted to confirm that the linked docs is still accurate? I have a few > > different use cases and may need to reference a client cert key pair in a > > JKS or perhaps from the windows certificate store for authentication to > the > > nexus repository. Is still a supported configuration by maven? I found > some > > references to support here: > https://issues.apache.org/jira/browse/MNG-1560 > > which references setting maven options for javax.net.ssl.* settings. > > Considering the environment, i'll probably need to be able to specify the > > key alias name too, just in case there's multiple certificates available. > > > > MNG-5583. I have intentionally closed this one since no was willing to > work on it. If someone wants to work on it, I'd be happy to discuss. >
