Versions Compared

Old Version 17

changes.mady.by.user Thijs Kinkhorst

Saved on

compared with

New Version 18

changes.mady.by.user Bas Zoetekouw

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • <organisation_id> identifies the organisation which has issues the specified identifier.  The format is a domain name as specified in RFC 1035. For use in SURFconext, this identifier MUST be equal to the organisation's schacHomeOrganization. 
  • <id_type> identifies the type of the identifier.  The following values are allowed:
    • empoyeeidemployeeid: the following id_token specifies an employee of the organisation
    • studentid: the following id_token specifies a student of the organisation
    • memberid: the following id_token specifies a person with some kind of generic membership of the organisation.  This could be used by organisations which use a common identifier for employees and students.

  • <id_token> is the internal identifier of the specified type, issued by the specified organisation.  Note that the identifier should be a proper URN, so the <id_token> may only consist of the characters specified in section 2.2 of RFC2141, i.e. only the following are allowed:

    • lower case letter (a-z)

    • capital letters (A-Z)

    • numbers (0-9)

    • the following special characters: ( ) + , . = @ ; $ _ ! * ' -

...