Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Last revisionBoth sides next revision | ||
en:metadata_admin_tool:checklist [2020/03/24 15:04] – Wolfgang Pempe | en:metadata_admin_tool:checklist [2021/07/20 09:57] – page about to be merged with en:checklist Silke Meyer | ||
---|---|---|---|
Line 14: | Line 14: | ||
* **Privacy Statement URL**: Please provide the link to your **data privacy statement**. This field is mandatory for Service Providers. If your data privacy statement is only available either in English or in German, you can leave the other field empty. | * **Privacy Statement URL**: Please provide the link to your **data privacy statement**. This field is mandatory for Service Providers. If your data privacy statement is only available either in English or in German, you can leave the other field empty. | ||
* The **logos** are displayed in the discovery service (favicons of IdPs) resp. on IdPs' login screens. That is why they have clearly defined maximum sizes. Please scale your logos to make them fit. The small logo is supposed to be a favicon of 16 by 16 pixels. (SPs do not need to submit a favicon URL.) The big logo has to have a width of 64 to 240 pixels and a maximum height of 180 pixels. | * The **logos** are displayed in the discovery service (favicons of IdPs) resp. on IdPs' login screens. That is why they have clearly defined maximum sizes. Please scale your logos to make them fit. The small logo is supposed to be a favicon of 16 by 16 pixels. (SPs do not need to submit a favicon URL.) The big logo has to have a width of 64 to 240 pixels and a maximum height of 180 pixels. | ||
- | * Please submit at least four **contacts** per system: An administrative contact, a technical one, a support contact and a security contact. We recommend to use non-personalized email addresses, especially for the security contact which could be your Computer Emergency Response Team. If you do not have anything like that, put in the contact that responds in case of security incidents. Please make sure to keep those email addresses up to date! | ||
- | * Have your X.509 certificate for SAML-based communication ready. We have an [[en: | ||
- | * IdPs use DFN-PKI certificates. As of July 2019, only the **second generation of DFN-PKI certificates** will be valid. | ||
- | * SPs can use DFN-PKI certificates (if entitled), certificates issued by established commercial CAs, or self-signed certificates. | ||
- | * SSL certificates must not exceed a **validity of 39 months**. | ||
- | * For security reasons, we do no longer accept certificates that were created with a sha1 **signature algorithm**. Here is how you can check this, e.g. with openssl: | ||
- | < | ||
- | openssl x509 -in example.org.crt.pem -noout -text | grep " | ||
- | </ | ||
- | * For Service Providers: If you need your SP to execute Attribute Queries or Artifact Queries, your SP certificate should have the client attribute set. If you request your certificate from DFN-PKI, please use the template called " | ||
- | < | ||
- | openssl x509 -in example.org.crt.pem -noout -text | grep -A 1 " | ||
- | X509v3 Extended Key Usage: | ||
- | TLS Web Client Authentication, | ||
- | </ | ||
- | |||
- | * Put your new system into our ** test federation** DFN-AAI-Test. Use our [[en: | ||
- | {{: | ||
- | * If it does, submit a request to join DFN-AAI. | ||
- | |||
- | {{: | ||