Exporting a client certificate - Revision history

Niklas Edmundsson (HPC2N): Swestore documentation moved

2023-02-08T09:56:20Z

Swestore documentation moved

Jens Larsson (NSC) at 13:15, 16 November 2020

2020-11-16T13:15:55Z

Niklas Edmundsson (HPC2N): Clarify that it's preferred to get new certs in browsers intead of transfer them

2017-01-12T08:36:39Z

Clarify that it's preferred to get new certs in browsers intead of transfer them

Niklas Edmundsson (HPC2N): Add navigation link back to digicert page

2017-01-12T08:17:57Z

Add navigation link back to digicert page

Niklas Edmundsson (HPC2N): Apple renamed OS X to macOS

2017-01-11T14:59:56Z

Apple renamed OS X to macOS

Jens Larsson (NSC) at 09:12, 20 June 2016

2016-06-20T09:12:51Z

Niklas Edmundsson (HPC2N): Add up/back link to SweGrid.

2013-05-22T14:16:06Z

Add up/back link to SweGrid.

Niklas Edmundsson (HPC2N): Update with dedicated pages.

2013-05-22T14:10:15Z

Update with dedicated pages.

Niklas Edmundsson (HPC2N): Add categories and "up" link.

2013-04-23T13:51:27Z

Add categories and "up" link.

Lars Viklund (HPC2N): Created page with "In order to use your client certificate for tasks other than authenticating your browser sessions, you need to export it to a protected file which you can import into browsers on..."

2013-03-20T13:27:28Z

Created page with "In order to use your client certificate for tasks other than authenticating your browser sessions, you need to export it to a protected file which you can import into browsers on..."

New page

In order to use your client certificate for tasks other than authenticating your browser sessions, you need to export it to a protected file which you can import into browsers on other machines, import into other browsers, and upload to SNIC resources where it can be used to generate proxy certificates for use with client tools.

The export process differs between operating systems and browsers, the following links outline the process for the common browsers and operating systems, resulting in a '''.p12''' or '''.pfx''' file.

* [[Exporting_a_client_certificate_on_Windows|Exporting on Windows (Chrome and Internet Explorer)]]
* [[Exporting_a_client_certificate_on_OS_X|Exporting on OS X (Chrome and Safari)]]
* [[Requesting_a_grid_certificate_using_the_Terena_eScience_Portal#Exporting_Terena_certificate_for_use_with_Grid_tools|Exporting from Firefox]]

← Older revision		Revision as of 09:56, 8 February 2023
Line 1:		Line 1:
−	~~[[Category:Grid computing]]~~	+	#REDIRECT[[Swestore Documentation Moved]]
−	~~[[Category:SweGrid user guide]]~~
−	~~[[Category:Swestore]]~~
−	~~[[Category:Swestore user guide]]~~
−
−	~~[[Getting started with SweGrid\|< Getting started with SweGrid]]~~
−
−	[[Swestore~~\|< Swestore]]~~
−
−	~~[[Requesting a grid certificate using the Sectigo SSO Portal\|< Requesting a grid certificate using the Sectigo SSO Portal]]~~
−
−
−	In order to use your client certificate for tasks other than authenticating your browser sessions, you might need to export it to a protected file which you can then import into browsers on other machines, import into other browsers, and upload to SNIC resources where it can be used to generate proxy certificates for use with client tools.
−
−	~~'''NOTE''': When possible, it is generally preferred (and easier) to obtain a new (additional) certificate in web browsers rather than transfer certificates between browsers/machines.~~
−
−	~~The export process differs between operating systems and browsers, the following links outline the process for the common browsers and operating systems, resulting in a '''.p12''' or '''.pfx''' file.~~
−
−	* [[Exporting_a_client_certificate_on_Windows\|Exporting on Windows (Chrome and Internet Explorer)]]
−	* [[Exporting_a_client_certificate_on_macOS\|Exporting on macOS (OS X) (Chrome and Safari)]]
−	* [[Exporting_a_client_certificate_from_Firefox\|Exporting a client certificate from Firefox]]
−	* [[Exporting_a_client_certificate_from_Chrome\|Exporting a client certificate from Chrome (Linux and other operating systems)]]

← Older revision		Revision as of 13:15, 16 November 2020
Line 8:		Line 8:
	[[Swestore\|< Swestore]]		[[Swestore\|< Swestore]]

−	[[Requesting a grid certificate using the ~~Digicert~~ SSO Portal\|< Requesting a grid certificate using the ~~Digicert~~ SSO Portal]]	+	[[Requesting a grid certificate using the Sectigo SSO Portal\|< Requesting a grid certificate using the Sectigo SSO Portal]]

← Older revision		Revision as of 08:36, 12 January 2017
Line 11:		Line 11:


−	In order to use your client certificate for tasks other than authenticating your browser sessions, you need to export it to a protected file which you can import into browsers on other machines, import into other browsers, and upload to SNIC resources where it can be used to generate proxy certificates for use with client tools.	+	In order to use your client certificate for tasks other than authenticating your browser sessions, you might need to export it to a protected file which you can then import into browsers on other machines, import into other browsers, and upload to SNIC resources where it can be used to generate proxy certificates for use with client tools.
		+
		+	'''NOTE''': When possible, it is generally preferred (and easier) to obtain a new (additional) certificate in web browsers rather than transfer certificates between browsers/machines.

	The export process differs between operating systems and browsers, the following links outline the process for the common browsers and operating systems, resulting in a '''.p12''' or '''.pfx''' file.		The export process differs between operating systems and browsers, the following links outline the process for the common browsers and operating systems, resulting in a '''.p12''' or '''.pfx''' file.

← Older revision		Revision as of 08:17, 12 January 2017
Line 7:		Line 7:

	[[Swestore\|< Swestore]]		[[Swestore\|< Swestore]]
		+
		+	[[Requesting a grid certificate using the Digicert SSO Portal\|< Requesting a grid certificate using the Digicert SSO Portal]]

@@ Line 14: / Line 14: @@
 * [[Exporting_a_client_certificate_on_Windows|Exporting on Windows (Chrome and Internet Explorer)]]
-* [[Exporting_a_client_certificate_on_OS_X|Exporting on OS X (Chrome and Safari)]]
+* [[Exporting_a_client_certificate_on_macOS|Exporting on macOS (OS X) (Chrome and Safari)]]
 * [[Exporting_a_client_certificate_from_Firefox|Exporting a client certificate from Firefox]]
 * [[Exporting_a_client_certificate_from_Chrome|Exporting a client certificate from Chrome (Linux and other operating systems)]]

@@ Line 1: / Line 1: @@
 [[Category:Grid computing]]
 [[Category:SweGrid user guide]]
-[[Category:SweStore]]
+[[Category:Swestore]]
-[[Category:SweStore user guide]]
+[[Category:Swestore user guide]]
 [[Getting started with SweGrid|< Getting started with SweGrid]]
-[[SweStore|< SweStore]]
+[[Swestore|< Swestore]]

← Older revision		Revision as of 13:51, 23 April 2013
Line 1:		Line 1:
		+	[[Category:Grid computing]]
		+	[[Category:SweGrid user guide]]
		+	[[Category:SweStore]]
		+	[[Category:SweStore user guide]]
		+	[[SweStore\|< SweStore]]
		+
		+
	In order to use your client certificate for tasks other than authenticating your browser sessions, you need to export it to a protected file which you can import into browsers on other machines, import into other browsers, and upload to SNIC resources where it can be used to generate proxy certificates for use with client tools.		In order to use your client certificate for tasks other than authenticating your browser sessions, you need to export it to a protected file which you can import into browsers on other machines, import into other browsers, and upload to SNIC resources where it can be used to generate proxy certificates for use with client tools.