FEDURUS Metadata

The metadata describe Identity Providers (IdP) and Service Providers (SP) of the respective federation. They are updated hourly, usually every full hour.

SAML 2.0 metadata

FEDURUS Federation
For SPs:: http://metadata.fedurus.ru/metadata.fedurus+idp.xml contains only IdPs
For IdPs: http://metadata.fedurus.ru/metadata.fedurus+sp.xml contains only SPs
Legacy: http://metadata.fedurus.ru/metadata.fedurus.xml contains all IdPs & SPs

The federation metadata files are digitally signed with the FEDURUS Metadata Signer certificate. This certificate should be configured as the trust anchor for PKIX-based validation of the metadata signature.

FEDURUS Metadata Signer certificate: DER format PEM format
Validity:2018-10-15 to 2028-10-12
SHA256 Fingerprint:8D:B3:F3:36:4D:97:ED:81:54:A9:0E:65:3D:D9:69:44:26:2E:46:B6:59:32:7A:BD:59:F8:9B:78:F0:5B:35:4E
SHA1 Fingerprint:1A:BF:7D:3B:04:F7:6E:14:54:13:0C:D0:08:B5:25:07:6C:5F:8E:64
Signed metadata files:metadata.fedurus.xml, metadata.fedurus+idp.xml, metadata.fedurus+sp.xml, metadata.edugain.xml

Update of Federation Metadata

AAI-enabled systems in the FEDURUS federation are requested to update the metadata at least daily. Hourly updates are strongly recommended in order to support fast propagation of metadata changes.

Instructions for configuring the above metadata with an automatic hourly refresh and signature validation based on the FEDURUS trust anchor can be found in our SP deployment guide and the IdP deployment guide, respectively (MetadataProvider elements in the XML configuration files).

If the SP or IdP downloading metadata is behind a firewall or proxy, please be aware that the IP address of the www.fedurus.ru host may change without notice. Creating IP-based filter rules is therefore discouraged, and we strongly recommend configuring the SP to use a proxy and the IdP to use a proxy instead.