|
|
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)]]
| |