Difference between revisions of "Exporting a client certificate"
(Apple renamed OS X to macOS) |
|||
| Line 14: | Line 14: | ||
* [[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_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 14:59, 11 January 2017
< 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.
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.
