About eduID

Hungarian Research and Educational Federation (HREF) is a SAML2-based Identity Federation of Hungarian higher education and research institutions, 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.

Policy and principles of interoperation

Basic principles

  1. The aim of the Federation is to allow the use of services of its Members and Partners, where authorisation is based on the user information originating from the users’ Home Institutions.
  2. Home Institutions must only authenticate users having a known affiliation to them.
  3. IdPs and SPs must not give false or misleading information about themselves.
  4. User information provided by IdPs should be as accurate as possible. SPs must take into account that parts of the received information may be at the discretion of the user.
  5. User credentials (i.e. passwords) stored by IdPs must be protected and verified only through secure procedures.
  6. SPs must request only the user attributes which are absolutely necessary for their operation.
  7. SPs must not ask users for their federation passwords.
  8. SPs must handle personal data according to the local privacy laws.
  9. IdPs and SPs must cooperate in the investigation of possible abuse/fraud.
  10. IT systems running IdPs and SPs must be operated with due diligence.

Data protection

  1. 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.
  2. Whenever the Data Protection Policy changes, the Federation Operator must be notified.
  3. Transfer of personal data is only allowed when either
    • authorised by law, or
    • the user expressed his or her consent on the data transfer.

Rules of membership

The Federation is operated by the Federation Operator, that also operates the national research network. Further participants are Members and Partners that must have a signed contract with the Operator.

  1. The following institutions may be Members of the federation:
    • Institutions of the higher education;
    • Institutions of the Hungarian Research Academy and other research institutions;
    • Institutions of secondary education;
    • Public collections.
  2. Any organisation might join as a Partner.
  3. All Members and Partners of the Federation might provide services.
  4. A Partner might participate in the meeting of the Members’ Board as an observer, without having rights to vote.
  5. Only Members are entitled to
    • supply user identity information to the federation
    • send representatives into the Members’ Board with a right to vote.


The governance body of the federation is the Members’ Board (MB). Every Federation Member may send one representative person to the Members’ Board, who has one vote.

The working language of the MB is Hungarian. The Board publishes its decisions and guidelines at Documents page.

    MB is authorised to

  • accept new Federation documents or modify existing ones,
  • accept application of new Members and Partners

Partners may also send representatives for MB meetings, without voting rights.


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 here.

Operational requirements


Attribute Specification is maintained in a separate document.

As a brief summary, the following attributes are mandatory or recommended:

IdPs may implement other attributes.

Mandatory attributes

  1. eduPersonPrincipalName
  2. eduPersonTargetedID
  3. eduPersonScopedAffiliation
  4. schacHomeOrganizationType

Recommended attributes

  1. eduPersonEntitlement
  2. mail
  3. displayName


Metadata Specification is maintained in a separate document.

How to join

Production federation

In order to join the production federation as a Partner, you need to send the following information:

  • SP metadata URL (HTTPS preferred)
  • Name of the SP
  • Brief description of the service
  • Service URL
  • Privacy policy URL
  • Administrative and technical contact names and mail addresses (non-personal preferred)
  • Required and optional attributes
  • Logo URL (optional, use of SSL is mandatory)
  • Helpdesk URL (optional)

This information should be sent to the Federation Operator via email. Two copies of the signed Service Agreement should be sent by traditional post, one copy will be returned after counter-signing.

After the application has been reviewed by the Federation Operator, it is forwarded to the Members’ Board. It usually takes 3-5 working days for the Board to accept the application, after which the entity metadata is be added to the production federation metadata.

Testing metadata

It is recommended that a new SP should be registered to the testing federation at first, which is much easier and a fully online process.

The following information is necessary to enter into the testing metadata:

  • SP metadata URL (HTTPS preferred)
  • Name of the SP
  • Administrative and technical contact names and mail addresses (non-personal preferred)
  • Required and optional attributes

You can ask for test accounts in our Virtual Home Organization. During testing, you might want to use the production federation metadata, because the VHO is present in both metadata files.

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.