Contains the user's surname.
Contains the user's given name.
Name of the person in a form the user (or his or her organization) probably wants to be shown.
Preferred address for the "to:" field of email to be sent to this person. The address in this attribute cannot be assumed to represent an organizationally-assigned contact address for a user established as part of a strong identity-proofing process.
A single value of the form user@scope, where scope is a DNS-like subdomain representing the security domain of the user ("foobar.samlidp.io" or own domain of the organization added to the Identity Provider on admin page) and user is an arbitrary persistent key which unambiguously maps to a person within an organization.
A single string value of no more than 256 characters that uniquely identifiers a user in an opaque, privacy-preserving fashion. The value will be different for a given user for each service provider to which a value is sent, to prevent correlation of activity between service providers.
Multiple values of the form value@scope, where scope is a DNS-like subdomain representing the organization or sub-organization of the affiliation ("foobar.samlidp.io" or own domain of the organization added to the Identity Provider on admin page) and value is one of:
Affiliation is a high-level expression of the relationship of the user to the university or organization specified in the scope. A user can possess many affiliations, though some values are mutually exclusive. This attribute is often made available to any service provider, and is a good way to filter or block users of a given general type. In particular, "member" is an indication that the user is somebody with relatively official standing with a university at the present time, and does not apply to guests, other temporary accounts, terminated employees, unpaid/unregistered students, and other exceptional cases.
The type of the organization, one of the following values:
Use attributes.samlidp.io for testing which attributes are released about a user. This is a real Service Provider, it knows all samlidp.io Identity Providers.
Your Identity Provider supports the Research and Scholarship Entity Category
When your users access a Service Provider which has the Research and Scholarship Entity Category the following attributes are released if consent is also given:
Your Identity Provider has a default scope under the samlidp.io domain. It is perfectly fine but for production usage we recommend to use a domain name that belongs to your organization. Before we start using your domain name as a scope, we verify that it exists and it is under your control. Please create a TXT record in your domain name's DNS zone with the content of the hash you can find in the IdP's edit page.
You can add any Service Provider exclusively for your Identity Provider, without participating any federation. It is a good option for testing purposes, or if a Service Provider is not part of the federation as your Identity Provider is.
You, as an administrator, can add users one by one, or upload the information about them in a CSV file. All fields are required, and after the user is created, the username cannot be modified.
You cannot set a password for a user. When you register or activate a user, a token will be sent to the user directly by email, using whic he or she can set their password. All passwords are strongly hashed and kept securely.
Setting user status
If a user is enabled, he or she can login via the Identity Provider, if disabled, it is not allowed. A user with disabled status can be enabled again anytime, but after one year, the user is removed from the user list.
If you delete a user, all data except from their username gets deleted immediately and irrevocably. The username is added to an internal list of deleted user identifiers in order to prevent future reassignment.
We know the following federations (approx. 8500 Service Providers). If you can't find the one you want to collaborate with, please do not hesitate to contact us.
|Federation||Contact URL||Contact email|
|Algeria - ARNaai||https://firstname.lastname@example.org|
|Armenia - AFIRE||http://email@example.com|
|Australia - AAF||https://firstname.lastname@example.org|
|Austria - ACOnet Identity Federation (eduID.at)||http://email@example.com|
|Belgium - Belnet Federation||http://firstname.lastname@example.org|
|Brazil - CAFe Federation||https://email@example.com|
|Canada - CAF Federation||https://firstname.lastname@example.org|
|Chile - COFRe Federation||https://email@example.com|
|China - CARSI Federation||http://firstname.lastname@example.org|
|Columbia - RENATA Federation||http://email@example.com|
|Croatia - AAI@eduHr Federation||http://firstname.lastname@example.org|
|Czech Republic - eduID.cz||https://email@example.com|
|Denmark - WAYF Federation||http://firstname.lastname@example.org|
|Ecuador - MINGA||https://email@example.com|
|Estonia - TAAT Federation||http://firstname.lastname@example.org|
|Finland - Haka||https://email@example.com|
|France - Fédération Éducation-Recherche||https://firstname.lastname@example.org|
|Germany - DFN-AAI||https://email@example.com|
|Greece - GRNET Federation||https://firstname.lastname@example.org|
|Grid IDentity Pool Federation||https://email@example.com|
|Hungary - eduID.hu Federation||https://firstname.lastname@example.org|
|India - INFLIBNET Access Management Federation||http://email@example.com|
|Ireland - Edugate Federation||https://firstname.lastname@example.org|
|Israel - IUCC Identity Federation||https://email@example.com|
|Italy - IDEM federation||https://firstname.lastname@example.org|
|Japan - GakuNin Federation||https://www.gakunin.jp/en-Joinemail@example.com|
|Latvia - LAIFE Federation||https://firstname.lastname@example.org|
|Lithuania - LITNET FEDI Federation||https://email@example.com|
|Luxembourg - eduID.lu Federation||http://firstname.lastname@example.org|
|Macedonia - AAIEduMk||https://aaiedu.mk/|
|Moldova - LEAF|
|Netherlands - SURFconext Federation||https://email@example.com|
|New Zealand - Tuakiri Federation||https://firstname.lastname@example.org|
|Norway - FEIDE Federation||https://email@example.com|
|Poland - PIONIER Federation||https://aai.pionier.net.pl/en/|
|Portugal - RCTSaai Federation||https://firstname.lastname@example.org|
|RENU Identity Federation|
|Russia - FEDUrus Identity Federation||http://email@example.com|
|Singapore Access Federation (SGAF)|
|Slovakia - safeID||https://firstname.lastname@example.org|
|Slovenia - ArnesAAI Federation||http://email@example.com|
|Spain - SIR Federation||https://firstname.lastname@example.org|
|Sweden - SWAMID Federation||http://email@example.com|
|Switzerland - SWITCHaai Federation||https://firstname.lastname@example.org|
|UK Access Management Federation|
|Ukraine - PEANO Federation||http://email@example.com|