The first thing I did, was follow the installation instructions, listed here, for installing as a service. Now that we got that out of the way, here’s how to install Nexus Repository Manager 3 on Windows with my lessons learned.

From there your browser and the server negotiate an encryption method and cipher to use for the session, and you then have a session where all data you send back and forth is encrypted.

The server must also have a private key stored for decryption purposes. Essentially, when you browse to an HTTPS site the server provides your computer with a certificate, which provides a number of things, among them, identification information about the server and a public key for your browser to use for encryption purposes. To ensure the server is who is who is says it is, and to provide a means for encryption, a certificate needs to be provided. SSL provides the ability for encrypted communication between a web browser and a server. These protocols are called SSL(Secure Sockets Layer) and TLS(Transport Layer Security), for simplicity’s sake, many people generally refer to both of these protocols under the umbrella of SSL, and so that is what I will do below. On top of HTTP, there can sit another protocol that encrypts the data you send. HTTP, is a protocol that pretty much every website uses to send information to your browser. If you don’t know anything about web certificates, here’s the 2 minute rundown.Īn important term to keep in mind, HTTPS means HyperText Transfer Protocol(HTTP) + (Secure). I always think I know what I’m doing, but every time I work on certificate management, I manage to work in circles, until I finally figure out the problem. If you are like me, SSL certificate management can be daunting. I wanted to share some lessons learned and help people avoid the problems I had.

I wanted to install Nexus Repository Manager 3 and serve traffic over HTTPS, but I ran into some issues. Setting up SSL with Nexus Repository Manager 3 on Windows

Install nexus 3