Print versionIn July 2007 the auEduPerson Working Group of the AAF Project surveyed identity managers on sets of common attributes and schemas. The survey was distributed via CAUDIT (Council of Australian University Directors of IT). The results are summarised here.
Responses
- 32 responses total
- 28 Australian universities and research institutions
- 4 New Zealand universities
Respondents were asked the following questions.
Consistent with similar policies in other federations, it is likely that AAF identity providers will need to be able to provide the following core attributes. Do you foresee any difficulties with any of these attributes for your institution?
Responses to this question, shown below, incidate that identity managers identified very few potential problems with the proposed core attributes; however, additional information was often requested regarding the attributes eduPersonEntitlement and eduPersonTargetedID.
| Yes, we could hold or generate this attribute | No, we would have problems with this attribute | Not enough information was supplied | |
| sn |
100% |
0% |
0% |
| cn |
100% |
0% |
0% |
| eduPersonPrincipalName | 94% 30 |
6% 2 |
0% 0 |
| eduPersonEntitlement | 56% 18 |
13% 4 |
31% 10 |
| eduPersonScopedAffiliation | 88% 28 |
9% 3 |
3% 1 |
| eduPersonTargetedID | 78% 25 |
3% 1 |
19% 6 |
Under the proposed policy, the following attributes are highly recommended. Do you foresee any difficulties with any of these for your institution?
Responses to this question indicate that identity managers identified few problems with proposed recommended attributes. Several identity managers indicated they would be reluctant to release the attribute mobile to a service provider, and several indicated they would not be able to populate preferredLanguage, userCertificate, or userSMIMECertificate.
| Yes, we could hold or generate this attribute | No, we would have problems with this attribute | Not enough information was supplied | |
| eduPersonAffiliation | 93% 28 |
7% 2 |
0% 0 |
| telephoneNumber | 91% 29 |
9% 3 |
0% 0 |
| postalAddress | 88% 28 |
9% 3 |
3% 1 |
| displayName | 100% 32 |
0% 0 |
0% 0 |
| givenName | 100% 32 |
0% 0 |
0% 0 |
| 100% 32 |
0% 0 |
0% 0 |
|
| mobile | 81% 26 |
19% 6 |
0% 0 |
| 0 | 87% 27 |
6% 2 |
6% 2 |
| preferredLanguage | 63% 20 |
34% 11 |
3% 1 |
| userCertificate | 61% 19 |
26% 8 |
13% 4 |
| userSMIMECertificate | 61% 19 |
26% 8 |
13% 4 |
In order to join the AAF, institutions should be able to comply with the proposed policy by 1 Jan 2008. Does this provide sufficient time for your institution?
Responses to this question indicate that significant work remains to be done within many institutions to enable them to join the AAF.
- Yes: 19 (59%)
- No: 13 (41%)