Commit e84482f0 authored by Niels van Dijk's avatar Niels van Dijk
Browse files

Added headings to descriptions, minor bugfixes

parent 21f91841
......@@ -3,7 +3,7 @@
"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.",
"explanation": "<b>A verbose set of attributes</b><br/>You can select individual attributes below to make the profile information more specific.",
"display": "A verbose set of attributes",
"uid": [
"jstiglitz"
......@@ -33,17 +33,17 @@
}
},
"Research and Scholarship": {
"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",
"message": "<b>This is the Research and Scholarship (R&S) Section</b><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",
"explanation": "<b>R&S: displayName</b><br/>This profile provides a R&S compatible attribute bundle with the name of the user name being provided in the 'displayname' attribute",
"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 seperate 'surname' and 'givenname' attributes",
"explanation": "<b>R&S: surname + givename</b></br>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",
"givenName": "Georg",
......@@ -51,7 +51,7 @@
"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 'displayname' and as seperate 'surname' and 'givenname' attributes. In addition the users affiliations are provided in the 'eduPersonScopedAffiliation' attribute",
"explanation": "<b>R&S: name and affiliation</b><br/>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",
......@@ -64,7 +64,7 @@
]
},
"account4": {
"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",
"explanation": "<b>R&S: ePPN and pseudonoymous epTID identifiers</b><br/>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",
......@@ -79,7 +79,7 @@
]
},
"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' (ePPN) as well as 'eduPersonTargetedID' (ePTID) which suggest the 'eduPersonPrincipalName' may not be a stable identifier, but may be reassigned at some point",
"explanation": "<b>R&S: display name, ePPN and transparent epTID identifiers</b><br/>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",
......@@ -87,7 +87,7 @@
"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' (ePPN) as well as 'eduPersonTargetedID' (ePTID) which suggest the 'eduPersonPrincipalName' (ePPN) may not be a stable identifier, but may be reassigned at some point",
"explanation": "<b>R&S: surname + givename, ePPN and transparent epTID identifiers</b><br/>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",
......@@ -96,7 +96,7 @@
"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' (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",
"explanation": "<b>R&S: surname + givename, ePPN and epTID identifiers</b><br/>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",
......@@ -110,8 +110,8 @@
]
},
"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' (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",
"explanation": "<b>R&S: surname + givename, ePPN and epTID identifiers</b><br/>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": "R&S: surname + givename, ePPN and epTID identifiers",
"eduPersonPrincipalName": "w_rontgen@idp.example.org",
"eduPersonTargetedId": "w_rontgen@idp.example.org",
"givenName": "Wilhelm",
......@@ -159,7 +159,7 @@
"isMemberOf": "urn:collab:org:aarc-project.eu"
},
"account11": {
"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",
"explanation": "<b>No member affiliation</b><br/>. 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"
......@@ -185,7 +185,7 @@
"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",
"explanation": "<b>Member only</b><br/>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"
......@@ -206,7 +206,7 @@
"isMemberOf": "urn:collab:org:aarc-project.eu"
},
"account12": {
"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.",
"explanation": "<b>Incorrect scoping of attributes</b><br/>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"
......@@ -230,7 +230,7 @@
"isMemberOf": "urn:collab:org:aarc-project.eu"
},
"account13": {
"explanation": "This profile has an invalid email address. Note that eduPersonPrincipleName (ePPN) is NOT an email adress, so having multiple @ signs is allowed there.",
"explanation": "<b>Invalid email address</b><br/> Note that eduPersonPrincipleName (ePPN) is NOT an email adress, so having multiple @ signs is allowed there.",
"display": "Test: invalid email adress",
"uid": [
"oburton"
......@@ -255,7 +255,7 @@
"isMemberOf": "urn:collab:org:aarc-project.eu"
},
"account16": {
"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.",
"explanation": "<b>No human-readable ePPN</b><br/>The eduPersonPrincipleName is intended as an identifier, but not perse something one 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"
......@@ -300,7 +300,7 @@
"isMemberOf": "urn:collab:org:aarc-project.eu"
},
"account18": {
"explanation": "Inconsistant user name<br>There are various fields that may hold (parts of the) user name. The values provided may not be consistent.",
"explanation": "<b>Inconsistant user names</b><br/>There are various fields that may hold (parts of the) user name. The values provided may not seem be consistent.",
"display": "Test: Inconsistant user name",
"uid": [
"viggo7"
......@@ -319,7 +319,7 @@
"isMemberOf": "urn:collab:org:aarc-project.eu"
},
"account19": {
"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",
"explanation": "<b>Non-ASCII UTF-8 values</b><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"
......@@ -345,7 +345,7 @@
]
},
"account20": {
"explanation": "Diacritical characters<br>As identity federation is a global endever, you may encounter attribute values with diacritical characters",
"explanation": "<b>Diacritical characters</b><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