Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
en:certificates [2021/09/03 10:42] – Wolfgang Pempe | en:certificates [2023/01/06 14:30] – Wolfgang Pempe | ||
---|---|---|---|
Line 13: | Line 13: | ||
=== DFN-PKI Certificates === | === DFN-PKI Certificates === | ||
- | For general information, please refer to https:// | + | For SAML-based communication, 3-year valid certificates from the [[https:// |
- | If you are entitled to request certificates issued by DFN-PKI, please select the " | + | |
=== Common Trusted CA Certificates === | === Common Trusted CA Certificates === | ||
Line 20: | Line 19: | ||
=== Own/Local CA === | === Own/Local CA === | ||
- | For institutions/ | + | For certificates from a local CA the same rues apply as for self-signed certificates, see below. |
- | **Note:** If required, local CAs can also be hosted by the DFN-PCA (contact: https:// | + | |
- | **Important: | + | |
- | A good guide to operating your own CA can be found [[https:// | + | |
- | Parameters to be considered: | + | |
- | * Root Private Key: RSA, 4096 Bit | + | |
- | * Validity of the root certificate: | + | |
- | * Validity of the issued certificates: | + | |
- | * Key length of the issued certificates: | + | |
- | * Signature algorithm: sha256 | + | |
- | * The CN of the issued certificate corresponds to the FQDN of the respective IdP/SP host. | + | |
=== Self-signed Certificates === | === Self-signed Certificates === | ||
- | Self-signed certificates may be used if they are not valid for longer than 39 months. For production, the CN (or the subject alternative names) of the certificate must at least contain the domain name of the SP. Ideally it should contain the complete host name. As for the technical details, please refer to the online documentation of [[https:// | + | Self-signed certificates may be used if they are not valid for longer than 39 months. For production, the CN (or the subject alternative names) of the certificate must at least contain the domain name of the SP. Ideally it should contain the complete host name. As for the technical details, please refer to the online documentation of [[https:// |
- | Before joining the DFN-AAI production federation, self-signed certificates have to be verified by the DFN-AAI operations team. For this purpose, the following options are available after you uploaded your certificate in the metadata administration tool: | + | |
- | * Send us the certificate in an S/ | + | |
- | * An alternative way is to offer us a possibility to download the certificate via https (e.g. via your SPs metadata handler or a download link to the file on your webserver). The SSL connection to the webserver has to be secured by a trusted CA certificate. | + | |
- | * If none of these options works for you, please get in touch with us (+49 30 884299-9124, | + | |
- | < | + | < |
**As for Service Providers that are already registered with another federation, the same certificate (i.e. the one registered with the other federation) may be used even if the aforementioned requirements are not met.** In this case, please drop a note to the DFN-AAI [[hotline@aai.dfn.de|helpdesk]]. | **As for Service Providers that are already registered with another federation, the same certificate (i.e. the one registered with the other federation) may be used even if the aforementioned requirements are not met.** In this case, please drop a note to the DFN-AAI [[hotline@aai.dfn.de|helpdesk]]. | ||
</ | </ | ||
Line 89: | Line 74: | ||
If there is another intermediate certificate, | If there is another intermediate certificate, | ||
- | If you use the Apache webserver, point the SSLCACertificateFile directive to your chain file. (See the example configuration on [[de:shibidp3prepare-http# | + | If you use the Apache webserver, point the SSLCACertificateFile directive to your chain file. (See the example configuration on [[de:shibidp: |
Once you have added you certificate chain, adapted your configuration and activated it you can verify it with OpenSSL: | Once you have added you certificate chain, adapted your configuration and activated it you can verify it with OpenSSL: |