By default, Tomcat stores a host's SSL certificate files as defined in the server.xml
file. For example:
The excerpt from the server.xml
file above shows that Tomcat will fetch the certificate files for the host www.site-name.com
from the disk, using the folder D:\certificates\site-name.com.
By default, these files are placed manually by the system administrator in the specified folder and Tomcat loads them when it starts up.
The purpose of this project is to change the standard way in which Tomcat finds and loads these files. The certificate files will no longer be defined in server.xml
and will not be available on disk when Tomcat boots. The new way to upload certificate files should be as follows:
1 - Tomcat receives an HTTPS request.
2 - Tomcat identifies the host informed in the request.
3 - Tomcat checks if certificate files for the host are already installed in the folder on the disk.
4 - If not, Tomcat loads the files from a MySQL database and then writes the files to the certificate folder on the disk.
5 - If the certificate files are already in the disk folder, Tomcat continues processing the request normally, using the files on disk.
The job involves studying the Tomcat source code, understanding how it manages the certificates on disk, changing its form of management to meet the requirements of this project, and finally compiling the new source code with the changes so that we can have a customized version of Tomcat.
The development must be all in Java and the source code of the custom classes must be delivered together with instructions on how to compile the new customized version of Tomcat.Category
: IT & ProgrammingSubcategory
: Web developmentWhat is the scope of the project?
: Small change or bugIs this a project or a position?
: ProjectI currently have
: I have specificationsRequired availability
: As neededRoles needed