Difference between revisions of "Exporting a client certificate"
(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...") |
m (Add categories and "up" link.) |
||
| 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. | ||
Revision as of 13:51, 23 April 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.
