Add support for norEduPerson tag in XML CAS response
To allow attributes to be retrieved from <norEduPerson> nested elements when there is no <cas:attributes> available in the XML CAS response file:
<cas:serviceResponse xmlns:cas="http://www.yale.edu/tp/cas">
<cas:authenticationSuccess>
<cas:user>UserName</cas:user>
<norEduPerson>
<mail>UserEmail</mail>
<sn>UserLastName</sn>
<gn>UserFirstName</gn>
</norEduPerson>
</cas:authenticationSuccess>
</cas:serviceResponse>
What is norEduPerson?
eduPerson is designed to support LDAP (Lightweight Directory Access Protocol) operations for campus directories designed to facilitate communication among higher education institutions. It consists of a set of data elements or attributes about individuals within higher education, along with recommendations on the syntax and semantics of the data that may be assigned to those attributes.
The norEdu classes add further attributes supplementing eduPerson/eduOrg in order to satisfy the requirements of the environment of the Nordic educational community, such as support for National Identity Numbers (norEduPersonNIN) and for the educational numbering and identifier schemes.
Further reading:
- https://docs.feide.no/schema/noredu/noredu_ch02.html#relationship-to-other-ldap-schemas
- http://software.internet2.edu/eduperson/internet2-mace-dir-eduperson-201602.html#Introduction
What is CAS?
CAS stands for Central Authentication Service. It provides NetID authentication and Single-Sign-On for web-based applications and protects thousands of websites at Yale:
- When your application has been CASified, your users are presented with a single, consistent login page to enter their NetID and Password.
- With the Single-Sign-On nature of CAS, individuals need only provide their NetID and Password once per browser session instead of for every site they navigate to.
- Applications that implement the CAS protocol never see the individual's password, providing a safe and secure means to authenticate.
CAS was developed by Yale University's Technology and Planning Group. As world-wide usage of the protocol expanded, support and maintenance of the system was turned over to JASIG (now Apereo).
Further reading:
If this project helps you reduce time to develop, you can give me a cup of coffee ☕️ :-)
