Commit 894f9645 authored by Niels van Dijk's avatar Niels van Dijk
Browse files

Updated accounts and added additional descriptions

parent 902d3a5b
{
"Generic attribute profile": {
"message": "This generic attributes Section contains a profile with many of the attributes that are in use within R&E identity federations. Note however it is unlikely you need all of these. In most cases, you should request a more specific attribute set which can be tested with the other profiles provided.",
"profiles": {
"account9": {
"explanation": "A verbose set of attributes. You can select individual attributes below to make the profile information more specific.",
"display": "A verbose set of attributes",
"uid": [
"jstiglitz"
],
"eduPersonTargetedID": "bd0916qef0c2e675b2def4ahe6w50b7d4bb4aae",
"schacHomeOrganization": "harvard-example.edu",
"eduPersonPrincipalName": "stiglitz@harvard-example.edu",
"cn": "Joseph Eugene Stiglitz",
"givenName": "Joseph",
"sn": "Stiglitz",
"displayName": "Joseph Stiglitz",
"mail": "stiglitz@harvard-example.edu",
"homePhone": "+1 827 675 3232",
"eduPersonOrcid": "http://orcid.org/0000-1111-2222-3333",
"eduPersonAffiliation": [
"member",
"faculty",
"student"
],
"eduPersonScopedAffiliation": [
"employee@harvard-example.edu",
"faculty@harvard-example.edu",
"member@harvard-example.edu"
],
"isMemberOf": "urn:collab:org:aarc-project.eu"
}
}
},
"Research and Scholarship": {
"message": "This is the Research ad Scholarship Section",
"message": "This is the Research and Scholarship (R&S) Section<br>R&S has been designed as a simple and scalable way to release minimal amounts of required personal data to Service Providers serving the Research and Scholarship Community.<br>The R&S accounts provide the various permutations of attributes you may recieve if you declare yourself an R&S service provider in eduGAIN",
"profiles": {
"account1": {
"explanation": "This profile provides a R&S compatible attribute bundle with the name of the user name being provided in the 'displayname' attribute",
"display": "John D. Rockefeller",
"display": "R&S: display name",
"eduPersonPrincipalName": "jrockefeller@idp.example.org",
"displayName": "John D. Rockefeller",
"mail": "John.D.Rockefeller@idp.example.org"
},
"account2": {
"explanation": "This profile provides a R&S compatible attribute bundle with the name of the user name being provided in both a 'displayname' attribute as well as seperate 'surname' and 'givenname' attributes",
"display": "Georg Ohm",
"explanation": "This profile provides a R&S compatible attribute bundle with the name of the user name being provided in seperate 'surname' and 'givenname' attributes",
"display": "R&S: surname + givename",
"eduPersonPrincipalName": "g_ohm@idp.example.org",
"displayName": "Georg Ohm",
"givenName": "Georg",
"sn": "Ohm",
"mail": "georg.ohm@idp.example.org"
},
"account3": {
"explanation": "This profile provides a R&S compatible attribute bundle with the name of the user name being provided as seperate 'surname' and 'givenname' attributes. In addition the users affiliations are provided in the 'eduPersonScopedAffiliation' attribute",
"display": "Joseph Weeler",
"explanation": "This profile provides a R&S compatible attribute bundle with the name of the user name being provided as 'displayname' and as seperate 'surname' and 'givenname' attributes. In addition the users affiliations are provided in the 'eduPersonScopedAffiliation' attribute",
"display": "R&S: name and affiliation",
"eduPersonPrincipalName": "jweeler@idp.example.org",
"givenName": "Joseph",
"sn": "Weeler",
"displayName": "Joseph Weeler",
"mail": "joseph.weeler@idp.example.org",
"eduPersonScopedAffiliation": [
"member@idp.example.org",
......@@ -31,12 +64,13 @@
]
},
"account4": {
"explanation": "This profile provides a R&S compatible attribute bundle with the name of the user name being provided as seperate 'surname' and 'givenname' attributes. Please note the usage of both 'eduPersonPrincipalName' as well as 'eduPersonTargetedID' which suggest the 'eduPersonPrincipalName' may not be a stable identifier, but may be reassigned at some point",
"display": "Anthony West",
"explanation": "This profile provides a R&S compatible attribute bundle with the name of the user name being provided as 'displayname' and as seperate 'surname' and 'givenname' attributes. Please note the usage of both 'eduPersonPrincipalName' (ePPN) as well as 'eduPersonTargetedID' (ePTID) which suggest the 'eduPersonPrincipalName' may not be a stable identifier, but may be reassigned at some point",
"display": "R&S: ePPN and pseudonoymous epTID identifiers",
"eduPersonPrincipalName": "awest@idp.example.org",
"eduPersonTargetedID": "bd09168cf0c2e675b2def0ade6f50b7d4bb4aae",
"givenName": "Anthony",
"sn": "West",
"displayName": "Anthony West",
"mail": "anthony.west@idp.example.org",
"eduPersonScopedAffiliation": [
"member@idp.example.org",
......@@ -45,16 +79,16 @@
]
},
"account5": {
"explanation": "This profile provides a R&S compatible attribute bundle with the name of the user name being provided in the displayname attribute. Please note the usage of both 'eduPersonPrincipalName' as well as 'eduPersonTargetedID' which suggest the 'eduPersonPrincipalName' may not be a stable identifier, but may be reassigned at some point",
"display": "Ben Bernanke",
"explanation": "This profile provides a R&S compatible attribute bundle with the name of the user name being provided in the displayname attribute. Please note the usage of both 'eduPersonPrincipalName' (ePPN) as well as 'eduPersonTargetedID' (ePTID) which suggest the 'eduPersonPrincipalName' may not be a stable identifier, but may be reassigned at some point",
"display": "R&S: display name, ePPN and transparent epTID identifiers",
"eduPersonPrincipalName": "bbernanke@idp.example.org",
"eduPersonTargetedId": "bbernanke@idp.example.org",
"displayName": "Ben Bernanke",
"mail": "bbernanke@idp.example.org"
},
"account6": {
"explanation": "This profile provides a R&S compatible attribute bundle with the name of the user name being provided as seperate 'surname' and 'givenname' attributes. Please note the usage of both 'eduPersonPrincipalName' as well as 'eduPersonTargetedID' which suggest the 'eduPersonPrincipalName' may not be a stable identifier, but may be reassigned at some point",
"display": "Alan Greenspan",
"explanation": "This profile provides a R&S compatible attribute bundle with the name of the user name being provided as seperate 'surname' and 'givenname' attributes. Please note the usage of both 'eduPersonPrincipalName' (ePPN) as well as 'eduPersonTargetedID' (ePTID) which suggest the 'eduPersonPrincipalName' (ePPN) may not be a stable identifier, but may be reassigned at some point",
"display": "R&S: surname + givename, ePPN and transparent epTID identifiers",
"eduPersonPrincipalName": "agreenspan@idp.example.org",
"eduPersonTargetedId": "agreenspan@idp.example.org",
"givenName": "Alan",
......@@ -62,8 +96,8 @@
"mail": "agreenspan6@idp.example.org"
},
"account7": {
"explanation": "This profile provides a R&S compatible attribute bundle with the name of the user name being provided in the displayname attribute. Please note the usage of both 'eduPersonPrincipalName' as well as 'eduPersonTargetedID' which suggest the 'eduPersonPrincipalName' may not be a stable identifier, but may be reassigned at some point. In addition the users affiliations are provided in the 'eduPersonScopedAffiliation' attribute",
"display": "André-Marie Ampère",
"explanation": "This profile provides a R&S compatible attribute bundle with the name of the user name being provided in the displayname attribute. Please note the usage of both 'eduPersonPrincipalName' (ePPN) as well as 'eduPersonTargetedID' (ePTID) which suggest the 'eduPersonPrincipalName' may not be a stable identifier, but may be reassigned at some point. In addition the users affiliations are provided in the 'eduPersonScopedAffiliation' attribute",
"display": "R&S: surname + givename, ePPN and epTID identifiers",
"eduPersonPrincipalName": "am_ampere@idp.example.org",
"eduPersonTargetedId": "am_ampere@idp.example.org",
"displayName": "André-Marie Ampère",
......@@ -76,7 +110,7 @@
]
},
"account8": {
"explanation": "This profile provides a R&S compatible attribute bundle with the name of the user name being provided as seperate 'surname' and 'givenname' attributes.Please note the usage of both 'eduPersonPrincipalName' as well as 'eduPersonTargetedID' which suggest the 'eduPersonPrincipalName' may not be a stable identifier, but may be reassigned at some point. In addition the users affiliations are provided in the 'eduPersonScopedAffiliation' attribute",
"explanation": "This profile provides a R&S compatible attribute bundle with the name of the user name being provided as seperate 'surname' and 'givenname' attributes.Please note the usage of both 'eduPersonPrincipalName' (ePPN) as well as 'eduPersonTargetedID' (ePTID) which suggest the 'eduPersonPrincipalName' may not be a stable identifier, but may be reassigned at some point. In addition the users affiliations are provided in the 'eduPersonScopedAffiliation' attribute",
"display": "Wilhelm Röntgen",
"eduPersonPrincipalName": "w_rontgen@idp.example.org",
"eduPersonTargetedId": "w_rontgen@idp.example.org",
......@@ -92,43 +126,12 @@
}
}
},
"Custom attributes": {
"message": "This is the Custom attributes Section",
"profiles": {
"account9": {
"explanation": "More expansive attribute list",
"display": "Joseph Stiglitz",
"uid": [
"jstiglitz"
],
"schacHomeOrganization": "harvard-example.edu",
"eduPersonPrincipalName": "stiglitz@harvard-example.edu",
"cn": "Joseph Eugene Stiglitz",
"givenName": "Joseph",
"sn": "Stiglitz",
"displayName": "Joseph Stiglitz",
"mail": "stiglitz@harvard-example.edu",
"homePhone": "+1 827 675 3232",
"eduPersonOrcid": "http://orcid.org/0000-1111-2222-3333",
"eduPersonAffiliation": [
"member",
"student"
],
"eduPersonScopedAffiliation": [
"employee@harvard-example.edu",
"faculty@harvard-example.edu",
"member@harvard-example.edu"
],
"isMemberOf": "urn:collab:org:aarc-project.eu"
}
}
},
"Behaviour tests": {
"message": "This is the beahaviour tests Section",
"message": "This is the beahaviour tests Section.<br>These tests offer a range of scenarios you could encounter when engaing with identity federations 'in the wild'. Use these tests to confirm compatilbility with various attribute useage scenrios and various values of attributes which may be delivered to your Service.",
"profiles": {
"account10": {
"explanation": "Test - multi-valued mail attribute.",
"display": "Jordan R. Belfort",
"explanation": "<b>Multi-valued mail attribute</b><br>The email attribute is multi valued, so you may recieve more then one of them. It is up to you to decide how to handle that.",
"display": "Test: Multi-valued mail attribute",
"uid": [
"belfort"
],
......@@ -156,8 +159,8 @@
"isMemberOf": "urn:collab:org:aarc-project.eu"
},
"account11": {
"explanation": "Test - No member affiliation ind eduPersonAffiliation.",
"display": "Steve Wynn",
"explanation": "No member affiliation. Even though this profile is asserted by the institutional identity provider, this user is not considered to be a member (so not student, nor factuly or staff) of the institution.<br>You can (and should) use the value of eduPersonAffiliation or eduPersonScopedAffiliation to evaluate this",
"display": "Test: No a member",
"uid": [
"wynn"
],
......@@ -168,25 +171,43 @@
"sn": "Wynn",
"displayName": "Steve Wynn",
"mail": [
"S.Wynn@harvard-example.edu",
"Steve.Wynn@example-casino.com",
"steve.Wynn@las.vegas.com"
"S.Wynn@harvard-example.edu"
],
"eduPersonAffiliation": [
"employee",
"faculty"
"alum",
"library-walk-in"
],
"eduPersonScopedAffiliation": [
"employee@harvard-example.edu",
"faculty@harvard-example.edu",
"member@harvard-example.edu"
"alum@harvard-example.edu",
"library-walk-in@harvard-example.edu"
],
"eduPersonEntitlement": "urn:mace:dir:entitlement:common-lib-terms-example",
"isMemberOf": "urn:collab:org:aarc-project.eu"
},
"account15": {
"explanation": "Member only. In this profile you can only learn about the fact that this user is a member of the institution, but not what the affilation is. This is a very common default setting",
"display": "Test: Member affiliation only",
"uid": [
"s_jobs"
],
"schacHomeOrganization": "idp.example.org",
"eduPersonPrincipalName": "student1@idp.example.org",
"cn": "Steven Paul Jobs",
"givenName": "Steve",
"sn": "Jobs",
"displayName": "Steve Jobs",
"mail": "steve.jobs@idp.example.org",
"eduPersonAffiliation": [
"member"
],
"eduPersonScopedAffiliation": [
"member@idp.example.org"
],
"isMemberOf": "urn:collab:org:aarc-project.eu"
},
"account12": {
"explanation": "Test - Incorrect domain scope for Home organisation",
"display": "Isaac Newton",
"explanation": "Incorrect scoping of attributes. In this case the instutition has multiple scopes in use (both .org and .edu). However, an assertion should only use scopes consistent with the md:scope element expressed in the IdP metadata. You should test this. Depending on your service provider software (e.g. Shibboleth), you may note incorrectly scoped attributes are filtered out already. Check you logs to confirm this.",
"display": "Test: Incorrect scoping",
"uid": [
"isaac"
],
......@@ -203,49 +224,24 @@
"eduPersonScopedAffiliation": [
"employee@huniversity-example.org",
"faculty@university-example.org",
"member@university-example.org"
"member@university-example.edu"
],
"eduPersonEntitlement": "urn:mace:dir:entitlement:common-lib-terms-example",
"isMemberOf": "urn:collab:org:aarc-project.eu"
},
"account13": {
"explanation": "Test - Invalid email address, note that ePPN is NOT an email adress, so having multiple @ signs is allowed",
"display": "Oscar Burton",
"explanation": "This profile has an invalid email address. Note that eduPersonPrincipleName (ePPN) is NOT an email adress, so having multiple @ signs is allowed there.",
"display": "Test: invalid email adress",
"uid": [
"oburton"
],
"schacHomeOrganization": "university-example.org",
"eduPersonPrincipalName": "o@burton@university-example.org",
"eduPersonPrincipalName": "ob@chemistry@university-example.org",
"cn": "Oscar Burton",
"givenName": "Oscar",
"sn": "Burton",
"displayName": "Oscar Burton",
"mail": "o@burton@university-example.edu",
"eduPersonAffiliation": [
"employee",
"member",
"staff"
],
"eduPersonScopedAffiliation": [
"employee@huniversity-example.org",
"staff@university-example.org",
"member@university-example.org"
],
"isMemberOf": "urn:collab:org:aarc-project.eu"
},
"account14": {
"explanation": "Test - Invalid ePPN",
"display": "Nikola Tesla",
"uid": [
"n_tesla"
],
"schacHomeOrganization": "university-example.org",
"eduPersonPrincipalName": "n_tesla@university-example.edu",
"cn": "Nikola Tesla",
"givenName": "Nikola",
"sn": "Tesla",
"displayName": "Nikola Tesla",
"mail": "n_tesla@university-example.org",
"mail": "ob@chemistry@university-example.org",
"eduPersonAffiliation": [
"employee",
"member",
......@@ -258,30 +254,9 @@
],
"isMemberOf": "urn:collab:org:aarc-project.eu"
},
"account15": {
"explanation": "Test - Member only",
"display": "Steve Jobs",
"uid": [
"s_jobs"
],
"schacHomeOrganization": "idp.example.org",
"eduPersonPrincipalName": "student1@idp.example.org",
"cn": "Steven Paul Jobs",
"givenName": "Steve",
"sn": "Jobs",
"displayName": "Steve Jobs",
"mail": "steve.jobs@idp.example.org",
"eduPersonAffiliation": [
"member"
],
"eduPersonScopedAffiliation": [
"member@idp.example.org"
],
"isMemberOf": "urn:collab:org:aarc-project.eu"
},
"account16": {
"explanation": "Test - Non human-friendly ePPN",
"display": "Bill Gates",
"explanation": "<b>No human-readable ePPN</b><br/>The eduPersonPrincipleName is intended as an identifier, but not as somethign you should represent to a user. Be aware the value might not contain a human readable value, as is the case in this profile.",
"display": "Test: No human-readable ePPN",
"uid": [
"FyHah7$J"
],
......@@ -303,17 +278,16 @@
"isMemberOf": "urn:collab:org:aarc-project.eu"
},
"account17": {
"explanation": "Test - Blank attribute values",
"display": "Michael Faraday",
"explanation": "<b>Blank attribute values</b><br/>Sending empty attribute values is uncommon, but not disallowed. This profile has empty 'surename' and 'giveName' attributes. The displayname is not empty, however it contains only spaces. Not very useful, but again not technically incorrect.",
"display": "Test: Empty attributes",
"uid": [
"m_faraday"
],
"schacHomeOrganization": "idp.example.org",
"eduPersonPrincipalName": "m_faraday@idp.example.org",
"cn": "",
"givenName": "",
"sn": "Faraday",
"displayName": "Michael Faraday",
"sn": "",
"displayName": " ",
"mail": "m_faraday@idp.example.org",
"eduPersonAffiliation": [
"member",
......@@ -326,8 +300,8 @@
"isMemberOf": "urn:collab:org:aarc-project.eu"
},
"account18": {
"explanation": "Test - Inconsistant user name",
"display": "Godfried Viggo",
"explanation": "Inconsistant user name<br>There are various fields that may hold (parts of the) user name. The values provided may not be consistent.",
"display": "Test: Inconsistant user name",
"uid": [
"viggo7"
],
......@@ -336,7 +310,7 @@
"cn": "Christian Godfried Viggo Lind",
"givenName": "Godfried",
"sn": "Viggo",
"displayName": "Godfried Viggo",
"displayName": "Viggo-Lind, G.",
"mail": "Godfried.Viggo@unidenmark-example.dk",
"eduPersonAffiliation": "student",
"eduPersonScopedAffiliation": [
......@@ -345,8 +319,8 @@
"isMemberOf": "urn:collab:org:aarc-project.eu"
},
"account19": {
"explanation": "Test - non-ASCII UTF-8 common name ",
"display": "Daisuke Takahashi",
"explanation": "Non-ASCII UTF-8 values (1)<br>As identity federation is a global endever, you may encounter attribute values with non UTF-8 characters",
"display": "Non-ASCII UTF-8 values (1)",
"uid": [
"U3342109"
],
......@@ -355,7 +329,7 @@
"cn": "Daisuke Takahashi, 髙橋 大輔",
"givenName": "Daisuke",
"sn": "Takahashi",
"displayName": "Daisuke Takahashi",
"displayName": "髙橋 大輔 (Takahashi, D.)",
"mail": "U3342109@exchange-example.edu",
"eduPersonAffiliation": [
"member",
......@@ -371,8 +345,8 @@
]
},
"account20": {
"explanation": "Test - Diacritical marks",
"display": "Martin N. Jørgensen",
"explanation": "Diacritical characters<br>As identity federation is a global endever, you may encounter attribute values with diacritical characters",
"display": "Test: Diacritical characters",
"uid": [
"jorgensen"
],
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment