The document discusses different authentication methods for various products. It defines authentication as determining if something is who it claims to be, while authorization is granting permission. It then lists some authentication options for MyHousing login pages, including LDAP, Active Directory, CAS, and custom authentication. For Conduct Coordinator, it mentions username, password, and token authentication, with authorization settings stored in the application.
3. Authentication vs. Authorization Authentication is the process of determining whether someone or something is, in fact, who or what it is declared to be. Authorization is the process of giving someone permission to do or have something. Authentication always precedes authorization A S U G 2010 Session T1
4. MyHousing Suite (3.2.4) login_student_url.cfm login_student_redirect.cfm login_student_local.cfm login_student_posted.cfm A S U G 2010 Session T1
6. login_student_posted.cfm Student is already authenticated (SSO, Portal) Need to set Session.StudentNumber Session.CampusID Need to secure Use a shared key Check CGI.HTTP_REFERER Use a certificate Need to redirect A S U G 2010 Session T1
7. Conduct Coordinator flexJO.html username password token DataSourceName.cfm alternate_authentication Authorization settings stored in CoCo A S U G 2010 Session T1
Editor's Notes
#5: login_student_url.cfm contains URL for re-direct when student has not yet logged in login_student_redirect.cfm allows a logged-in student to select which ASI to continue into (Apply Online or MyHousing) Login_student_local.cfm collect student is/password from form and check login Login_student_posted.cfm portal or other SSO option