== Purpose of this document ==
This document is a collection of the information specified in several specific documents written in Hungarian. Since only Hungarian educational and research institutions are expected to be Federation Members (ie. operate an Identity Provider), this document focuses on rules what are relevant to (international) Federation Partners.
== About the federation ==
Hungarian Research and Educational Federation ('''HREF''') is an identity federation a SAML2-based Identity Federation of Hungarian higher education and research institutions, and for public collections and other content providers. For the end-users, the federation aims to be transparent, therefore the login procedure is communicated as '''''eduID login'''''.
=== Contacts ===
The Federation is operated by [http://www.niif.hu NIIF Institute] as a Federation Operator. Questions, concerns or any kind of requests about the Federation should be directed to any of the following addresses:
:Hungary
News and information about the federation is located published at http://eduid.hu (Hungarian only)
=== Policy and principles of interoperation ===
==== Basic principles ====
* Prior joining the federation, every entity needs to publish the Data Protection Policy under which it operates. This policy must be kept up-to-date.
* Whenever the Data Protection Policy changes, the Federation Operator must be notified.
* Transfer of personal data is only allowed wheneither** authorised by law,or
** the user expressed his or her consent on the data transfer.
#* Institutions of secondary education;
#* Public collections.
# Any organisation might join as a '''PartnersPartner'''.
# All Members and Partners of the Federation might provide services.
# A Partner might participate in the meeting of the Members' Board as an observer, without having rights to vote.
# Only Members are entitled to
#* supply user identity information to the federation
#* send representatives into the Members' Board with a right to vote.
* accept application of new Members and Partners
Partners are may also may send representatives for MB meetings, without voting rights.
=== Legal ===
The Federation itself is not a legal entity, Members and Partners establish a legal connection to the Federation Operator. Any legal claims between Members and/or Partners shall be directed to the organisation operating the Identity Provider or the Service Provider. The Service Agreement between the Federation Operator and Partner is available '''[http://www.eduid.hu/wp-content/uploads/2012/08/href-contract-partner.doc here]'''.
== Technical information ==
=== Metadata ===
Information about the entities of the Federation [[HREFMetadataSpecEN | Metadata Specification]] is maintained in a signed XML separate document, called the federation metadata.==== Availability ====The metadata file is available both at http://metadata.eduid.hu/current/href.xml and https://metadata.eduid.hu/current/href.xml, however the unencrypted method is preferred. The file is stored on a highly available file server. The information inside the metadata file must not be trusted after the date specified in the <code>validUntil</code> field of the topmost <code>EntitiesDescriptor</code>. The expiration date of a metadata file is '''7 days''' after the date of the signature.
The metadata file is re-signed daily or whenever the entity information changes (eg. entities are added or modified). Entities are expected == How to refresh metadata information regularly.join ==== Trust in metadata =Production federation ======== Verification of In order to join the production federation as a Partner, you need to send the following information:* SP metadata file =====URL (HTTPS preferred)The contents * Name of the metadata file must be trusted only if the signature SP* Brief description of the Federation Operator can be validated.service* Service URL* Privacy policy URL* Administrative and technical contact names and mail addresses (non-personal preferred)* Required and optional attributes* Logo URL (optional)* Helpdesk URL (optional)
The This information should be sent to the Federation Operator uses a self-signed certificate for signing the metadata file, therefore the signing key must be explicitly trusted(see [[#Contacts|above]]) in email. Properties Two copies of the signing certificatesigned Service Agreement (available at http:* DN: <code>C=HU, O=NIIF Institute, OU=eduID Federation Operator, CN=Metadata Signer/emailAddress=aai@niif/eduid.hu</code>* MD5 fingerprint: <code>21:8C:BE:B4:D1:D6:12:C4:67:9F:16:FA:93:36:F6:A4</code>* SHA1 fingerprint: <code>FE:AE:0B:E8:FB:59:ED:F7:CB:7F:69:DF:19:4F:8B:6D:C7:F6:96:66</code>* Availability: from <code>Oct 5 08:18:46 2011 GMT</code> until <code>Sep 30 08:18:46 2031 GMT</code>documents) should be sent by traditional post, one copy will be returned after counter-signing.
The certificate used for signing can be downloaded from https://metadata.eduid.hu/href-metadata-signer-2011.crt , which link should lead to a page without certificate warnings with most browsers. It is recommended to request After the signing certificate from application has been reviewed by the Federation Operator by using other verifiable transport as well (such as PGP-signed email).===== Signing procedure =====Information about the entities , it is retrieved from forwarded to the Resource Registry by using strong server authenticationMembers' Board. If It usually takes 3-5 working days for the Board to accept the contents of application, after which the entity metadata changes, it is saved be added to a version control system and sent to a public mailing list ([https://listservthe production federation metadata.niif.hu/mailman/listinfo/href-metadata-changes href-metadata-changes])
The signature is done by a PIN-protected hardware token.===== Signing key change or revocation =====Changes of the signing key/certificate is always negotiated with the technical contacts of all federation entities.==== Authenticating peer entities =Testing metadata ===It is recommended for all entities to use self-signed certificates, however, even if an entity uses that a certificate signed by an external CA, it shall not new SP should be assumed that peers use any kind of path validation or revocation checking.===== Entity certificate change or revocation =====An entity should change its signing certificate by allowing a time frameregistered to the testing federation at first, when both the old which is much easier and the new certificate is available in the metadataa fully online process.
If an entity certificate is compromised, the Federation Operator must be notified immediately. The certificate following information is removed from necessary to enter into the testing metadata:* SP metadata URL (HTTPS preferred)* Name of the SP* Administrative and either replaced by a new one or the entity is removed from the metadata file. On such an incident, all technical contacts are notified to do an immediate metadata refresh to shorten the attack window.contact names and mail addresses (non-personal preferred)* Required and optional attributes
==== Metadata extensions ======== Other You can ask for test accounts in our Virtual Home Organization. During testing, you might want to use the production federation metadata sets available ====, because the VHO is present in both metadata files.
== Federation Operator services ==You do not need to re-register your entity to proceed to the production federation. If we have all the necessary information, the starting of the joining process is at your discretion.=== Metadata distribution ====== Resource Registry ====== Discovery Service ====== Virtual Home Organization ===[[Kategória: AAI]][[Kategória: eduid]][[Kategória: english]]
