Difference between revisions of "Certificate Authentication"
Jump to navigation
Jump to search
(Created page with "The Fusion Registry supports authentication via the use of an X509 certificate (in the PKCS12 format). In order to support Certificate Authentication the Fusion Registry must...") |
|||
| Line 1: | Line 1: | ||
| + | [[Category:RegistrySecurity]] | ||
The Fusion Registry supports authentication via the use of an X509 certificate (in the PKCS12 format). In order to support Certificate Authentication the Fusion Registry must be configured to communicate via the HTTPS protocol. | The Fusion Registry supports authentication via the use of an X509 certificate (in the PKCS12 format). In order to support Certificate Authentication the Fusion Registry must be configured to communicate via the HTTPS protocol. | ||
Certificate Authentication makes use of the servlet container (for example Apache Tomcat) which is the application responsible for Authenticating the request. When the Fusion Registry recieves the request, it has been pre-authenticated by the | Certificate Authentication makes use of the servlet container (for example Apache Tomcat) which is the application responsible for Authenticating the request. When the Fusion Registry recieves the request, it has been pre-authenticated by the | ||
Revision as of 03:52, 11 February 2020
The Fusion Registry supports authentication via the use of an X509 certificate (in the PKCS12 format). In order to support Certificate Authentication the Fusion Registry must be configured to communicate via the HTTPS protocol.
Certificate Authentication makes use of the servlet container (for example Apache Tomcat) which is the application responsible for Authenticating the request. When the Fusion Registry recieves the request, it has been pre-authenticated by the
