Certificate Authentication - Revision history

Vmurrell: /* Testing */

2025-10-06T10:12:20Z

‎Testing

Vmurrell: /* Configuring Tomcat for Certificates */

2025-10-06T10:09:36Z

‎Configuring Tomcat for Certificates

Vmurrell: /* Generate a certificate for the client of Fusion Metadata Registry */

2025-10-06T10:07:14Z

‎Generate a certificate for the client of Fusion Metadata Registry

Vmurrell: /* Generate a certificate for the client of Fusion Metadata Registry */

2023-09-12T08:57:49Z

‎Generate a certificate for the client of Fusion Metadata Registry

Mnelson: /* Testing */

2022-09-26T14:02:04Z

‎Testing

Mnelson: /* Testing */

2022-09-26T14:01:57Z

‎Testing

Mnelson: /* Link Certificate to Organisations */

2022-09-26T14:01:41Z

‎Link Certificate to Organisations

Mnelson: /* Testing */

2022-09-26T14:00:33Z

‎Testing

Mnelson at 13:59, 26 September 2022

2022-09-26T13:59:43Z

Mnelson at 10:52, 11 February 2020

2020-02-11T10:52:52Z

@@ Line 77: / Line 77: @@
 Alternatively a test can be performed in code such as Java, see the following code snippet which requests information from a secure resource.  The expected response will simply be an empty JSON array.  If the user associated with the certificate does not have admin permissions or if the certificate is not being checked correctly, then the response will be an error or HTML text representing a redirect to the HTML home page.
-[[File:Example code test.PNG|800px]]
+[[File:Example code test.png|800px]]
 ==Troubleshooting==

@@ Line 59: / Line 59: @@
 . Modify the [tomcat]/conf/server.xml
-[[File:Modify server.PNG|300px]]
+[[File:Modify server.png|300px]]
 ==Set up Security Permissions==

@@ Line 28: / Line 28: @@
 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 Metadata Registry===
+===Generate a certificate for the client of Fusion 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:

← Older revision		Revision as of 08:57, 12 September 2023
Line 36:		Line 36:
	keytool -genkeypair -alias regClient -keyalg RSA -validity 365 -keystore regClient.p12 -storetype PKCS12		keytool -genkeypair -alias regClient -keyalg RSA -validity 365 -keystore regClient.p12 -storetype PKCS12

−	[[File:Example p12.~~PNG~~\|600px]]	+	[[File:Example p12.png\|600px]]

@@ Line 70: / Line 70: @@
 # Launch the Fusion Registry web application.
 # Open your Chose Web Browser and in the Settings area, navigate to ‘Manage Certificates if you are suing Chrome or View Certificates if you are using Firefox’.
 # Load the registry client certificate into the web browser (regClient.p12 for example)
 # Navigate to the Fusion Registry web page using https.  The web browser may ask which certificate you wish to use: select 'regClient'.  The Fusion Registry application should show the user as being logged in, and it will not be possible to log out.

@@ Line 61: / Line 61: @@
 [[File:Modify server.PNG|300px]]
-==Link Certificate to Organisations==
+==Set up Security Permissions==
-Once a Certificate has been added to the tomcat truststore, it will be used to authenticate the request.
+Open the Fusion Security Manager. Add a Group ID which matches the CNAME of the Certificate. Then add security read/write rules for the Group ID.
 ==Testing==

@@ Line 76: / Line 76: @@
 To test Certificate Authentication:
-# Launch the FMR web application.
+# Launch the Fusion Registry web application.
 # Open your Chose Web Browser and in the Settings area, navigate to ‘Manage Certificates if you are suing Chrome or View Certificates if you are using Firefox’.
 [[File:View Certificates - Chrome.PNG|thumb|Chrome]]
@@ Line 82: / Line 82: @@
 [[File:Manage Certivicates - Firefox.PNG|thumb|Firefox]]
 # Load the registry client certificate into the web browser (regClient.p12 for example)
-# Navigate to the FMR web page using https.  The web browser may ask which certificate you wish to use: select 'regClient'.  The FMR application should show the user as being logged in, and it will not be possible to log out.
+# Navigate to the Fusion Registry web page using https.  The web browser may ask which certificate you wish to use: select 'regClient'.  The Fusion Registry application should show the user as being logged in, and it will not be possible to log out.
 Alternatively a test can be performed in code such as Java, see the following code snippet which requests information from a secure resource.  The expected response will simply be an empty JSON array.  If the user associated with the certificate does not have admin permissions or if the certificate is not being checked correctly, then the response will be an error or HTML text representing a redirect to the HTML home page.
 Alternatively a test can be performed in code such as Java, see the following code snippet which requests information from a secure resource.  The expected response will simply be an empty JSON array.  If the user associated with the certificate does not have admin permissions or if the certificate is not being checked correctly, then the response will be an error or HTML text representing a redirect to the HTML home page.

@@ 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.
-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
+= Authentication =

← Older revision		Revision as of 10:52, 11 February 2020
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