Difference between revisions of "Exporting a client certificate"

From SNIC Documentation
Jump to: navigation, search
(Update with dedicated pages.)
(Clarify that it's preferred to get new certs in browsers intead of transfer them)
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
[[Category:Grid computing]]
 
[[Category:Grid computing]]
 
[[Category:SweGrid user guide]]
 
[[Category:SweGrid user guide]]
[[Category:SweStore]]
+
[[Category:Swestore]]
[[Category:SweStore user guide]]
+
[[Category:Swestore user guide]]
[[SweStore|< SweStore]]
 
  
 +
[[Getting started with SweGrid|< Getting started with SweGrid]]
  
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.
+
[[Swestore|< Swestore]]
 +
 
 +
[[Requesting a grid certificate using the Digicert SSO Portal|< Requesting a grid certificate using the Digicert 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.
 
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_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_Firefox|Exporting a client certificate from Firefox]]
 
* [[Exporting_a_client_certificate_from_Chrome|Exporting a client certificate from Chrome (Linux and other operating systems)]]
 
* [[Exporting_a_client_certificate_from_Chrome|Exporting a client certificate from Chrome (Linux and other operating systems)]]

Revision as of 08:36, 12 January 2017


< Getting started with SweGrid

< Swestore

< Requesting a grid certificate using the Digicert 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.