If the certificate is already added, the button can undo this operation and will read Remove certificate from trust store . This feature is analogous to going to the SSL Certificates user interface and using the Load certificate button found there as described in Outbound SSL - Trusting SSL Certificates Globally.
To confirm trust of the remote certificate, click the Add certificate to truststore button in the dialog. This specifically also includes usage of self-signed certificates used in your organization. Use the Certificate Details dialog when the remote certificate is not issued by a well-known public certificate authority included in the default Java trust store. An example is shown in Figure: “Certificate Details Dialog to Add an SSL to the Nexus Truststore”.įigure: Certificate Details Dialog to Add an SSL to the Nexus Truststore The View certificate button triggers the display of the SSL Certificate Details dialog. It is only displayed, if the remote storage uses a HTTPS URL. It allows you to manage the SSL certificate of the remote repository and solves these problems. The Proxy configuration for each proxy repository documented in Managing Repositories and Repository Groups includes a section titled Use the Nexus truststore. When the SSL certificate of a remote proxy repository is not trusted, the repository may be automatically blocked outbound requests fail with a message similar to "PKIX path building failed". Outbound SSL - Trusting SSL Certificates of Remote RepositoriesĪvailable in Nexus Repository OSS and Nexus Repository Pro and manual or scripted usage of the REST APIs.web browser HTTPS access to the user interface,.specialized authentication realms such as the Crowd realm.for SMTP/email integration documented in Email Server a remote proxy repository over HTTPS - documented in Repository Management.Outbound client communication may include integration with: Secure communication can be inbound or outbound. Using Secure Socket Layer (SSL) communication with the repository manager is an important security feature and a recommended best practice.
0 kommentar(er)
