Configure X509 Certificate Authentication - Revision history

Vmurrell at 10:22, 28 March 2024

2024-03-28T10:22:01Z

2024-03-27T15:33:55Z

‎Generate a certificate for the client of Fusion Metadata Registry

2024-03-25T12:47:57Z

2024-03-23T12:09:26Z

2022-09-05T13:52:45Z

2022-08-25T13:16:36Z

2022-07-21T12:53:47Z

‎Authentication via Certificates

2022-07-21T12:53:13Z

‎Authentication via Certificates

2022-07-21T12:22:13Z

‎Generate a certificate for the client of Fusion Registry

2022-07-21T12:19:26Z

‎Authentication via Certificates

@@ Line 1: / Line 1: @@
-[[Category:Draft_-_Installation_and_Configuration]]
+[[Category:Installation_and_Configuration]]
 [[Category:RegistrySecurity]]
 [[Category:FMR_Configuration_Reference]]

@@ Line 45: / Line 45: @@
 . Export the certificate from the p12 file to a .cer file
-  keytool -exportcert -alias regClient –keystore regClient.p12 –storetype PKCS12 –file regClient.cer
+  keytool -exportcert -alias regClient -keystore regClient.p12 -storetype PKCS12 -file regClient.cer
 ==Configuring Tomcat for Certificates==

@@ Line 1: / Line 1: @@
 [[Category:Draft_-_Installation_and_Configuration]]
+[[Category:RegistrySecurity]]
 [[Category:FMR_Configuration_Reference]]
 [[Category:How_To V11]]

← Older revision		Revision as of 12:09, 23 March 2024
Line 1:		Line 1:
		+	[[Category:Draft_-_Installation_and_Configuration]]
		+
	[[Category:FMR_Configuration_Reference]]		[[Category:FMR_Configuration_Reference]]
	[[Category:How_To V11]]		[[Category:How_To V11]]

@@ Line 1: / Line 1: @@
 [[Category:FMR_Configuration_Reference]]
-[[Category:How_To]]
+[[Category:How_To V11]]
 =Authentication via Certificates=

@@ Line 5: / Line 5: @@
 '''Important Note:''' Certificate Authentication will only work if HTTPS is enabled on the Web Server.
-Fusion Meta Data Registry (FMR)supports authentication via the use of an X509 certificate (in the PKCS12 format).<br>
+Fusion Meta Data Registry (FMR)supports authentication via the use of an X509 certificate (in the PKCS12 format). The Web Application Container WAC (e.g. Tomcat) must be configured to trust the certificate as the WAC is responsible for authenticating the Certificate.
-The Web Application Container WAC (e.g. Tomcat) must be configured to trust the certificate as the WAC is responsible for authenticating the Certificate.
+When the request is passed onto the FMR, it will attempt to map the Certificate to a FMR user.
-To support a new Certificate, log into the FMR as an Admin user, and navigate to Security -> Certificate Manager.   <br>
+To add support for a Certificate, log into the FMR as an Admin user, and navigate to Security -> Certificate Manager. New Certificates are added by clicking on the cogs icon and selecting Create New Certificate Definition.
 [[File:Certificate Manager Page.PNG|1000px]]

@@ Line 31: / Line 31: @@
 This process makes use of '''Java Keytool''' this is a command line application for certificate creation and management.
-===Generate a certificate for the client of Fusion Registry===
+===Generate a certificate for the client of Fusion Metadata Registry===
 This process creates a self-signed certificate to be given to the user of the Fusion Registry.  This certificate contains the user’s username in the Certificates Common Name (CN).  This process consists of two steps as follows:

@@ Line 6: / Line 6: @@
 The Web Application Container WAC (e.g. Tomcat) must be configured to trust the certificate as the WAC is responsible for authenticating the Certificate.
-''Certificate Authentication will only work if HTTPS is enabled''''' (is this correct - if so where do you do that?'''<br>
+''Certificate Authentication will only work if HTTPS is enabled''''' (is this correct - if so where do you do that?)'''<br>
 When the request is passed onto the FMR, it will attempt to map the Certificate to a FMR user. <br>