Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revisionLast revisionBoth sides next revision | ||
en:metadata_local [2021/03/02 11:00] – [Local Metadata] Silke Meyer | en:metadata_local [2023/03/02 12:29] – updated text to new MDV Silke Meyer | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | FIXME **This page is not fully translated, yet. Please help completing the translation.**\\ //(remove this paragraph once the translation is finished)// | ||
- | |||
====== Local Metadata ====== | ====== Local Metadata ====== | ||
Line 15: | Line 13: | ||
* protected web servers of the institution | * protected web servers of the institution | ||
- | Diese Dienste sollen i.d.R. //nicht// von anderen Einrichtungen genutzt werden können. Sie gehören daher //nicht// in die DFN-AAI oder die DFN-AAI-Basic. Die Metadatenverwaltung bietet eine andere Möglichkeit: | + | These services shall in general not be accessible for members of other home institutions. That is why you do not let them join DFN-AAI or DFN-AAI-Basic. The [[https://www.aai.dfn.de/verwaltung/ | Metadata Administration Tool]] offers a different solution: You can activate the automatic generation of a so-called local metadata file that will only contain your IdP and your in-house SPs. It is thus specific to your institution. All local metadata files are generated hourly: They can be fetched from static URLs to make sure that the IdP and all local SPs always have up-to-date and valid metadata. **The big advantage:** Metadata can be maintained in a single place. Changes will then propagate to all participating systems (that fetch the local metadata regularly) automatically. If you maintain your in-house |
- | Ein weiterer Vorteil für Sie: Wenn Sie hausinterne Dienste als lokale SPs in die Metadatenverwaltung einpflegen, werden Sie vor Ablauf der Zertifikate genau so von uns informiert wie bei den Systemen in den Föderationen. | ||
- | ===== Aktivierung | + | ===== Local Metadata |
- | Diese Option kann in der [[https:// | + | We start to generate a local metadata file for your organization when you add your first SP to local metadata. You can find the download URL in the metadata administration tool, in the overview of your organization, |
- | Beispiel Schaltfläche " | + | You can optionally limit access to the download URL to certain IP address ranges. |
- | {{: | + | |
- | Anschließend können der IdP und die gewünschten SPs in die lokalen Metadaten aufgenommen werden: | + | {{:en: |
- | {{: | + | ====== Configuration ====== |
+ | ===== Shibboleth IdP ===== | ||
- | Der URL für die lokalen Metadaten einer Einrichtung hat das Format | + | Add an additional ''< |
- | {{: | + | <callout color="# |
- | + | Please replace the number | |
- | ====== Konfiguration ====== | + | |
- | ===== Shibboleth IdP ===== | + | |
- | Für die lokalen Metadaten muss in '' | + | |
- | <callout color="# | + | |
- | Bitte ersetzen Sie die " | + | |
</ | </ | ||
Line 49: | Line 41: | ||
xsi: | xsi: | ||
backingFile=" | backingFile=" | ||
- | metadataURL=" | + | metadataURL=" |
maxRefreshDelay=" | maxRefreshDelay=" | ||
< | < | ||
Line 58: | Line 50: | ||
xsi: | xsi: | ||
backingFile=" | backingFile=" | ||
- | metadataURL=" | + | metadataURL=" |
maxRefreshDelay=" | maxRefreshDelay=" | ||
< | < | ||
Line 72: | Line 64: | ||
===== Shibboleth SP ===== | ===== Shibboleth SP ===== | ||
- | Beim Shibboleth SP fügt man in ''/ | + | Add an additional metadata provider |
<file xml / | <file xml / | ||
... | ... | ||
- | < | + | < |
| | ||
< | < | ||
Line 82: | Line 74: | ||
... | ... | ||
</ | </ | ||
- | {{tag>lokale-metadaten}} | + | {{tag>local-metadata metadata}} |