Difference between revisions of "Exporting a client certificate"
m (Add categories and "up" link.) |
(Update with dedicated pages.) |
||
| Line 12: | Line 12: | ||
* [[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_OS_X|Exporting on 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)]] | ||
Revision as of 14:10, 22 May 2013
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.
