Project

General

Profile

Development #2779

CAS Authentication

Added by Benjamin Dauvergne over 6 years ago. Updated over 2 years ago.

Status:
Nouveau
Priority:
Bas
Assignee:
-
Category:
-
Target version:
Start date:
18 Apr 2013
Due date:
% Done:

0%

Patch proposed:
No
Planning:
No

Description

Implementation of the classic login password login can be used as a model authentic2/auth2_auth/backend.py. The reference specification at address http://www.jasig.org/cas/protocol gives details. It should support multiple CAS providers. For each provider a domain name can be specified (to differentiate homonyms).

A special Django authentication backend1 must also be implemented as there won't be any password to authenticate; this special backend will receive a username and eventually a domain and log the given user in. The key for the username should not be username which is already used by classical login/password backends. Link with real users could be done solely on the username or using a link table (linking existing users to users from the CAS provider).

Extraction of user attributes from CAS tickets is also linked to this ticket [2].

[1]: https://docs.djangoproject.com/en/1.4/ref/authbackends/
[2]: http://jasig.275507.n4.nabble.com/CAS-attributes-and-how-they-appear-in-the-CAS-response-td264272.html and https://issues.jasig.org/browse/CAS-655

History

#1 Updated by Benjamin Dauvergne over 6 years ago

  • Target version set to future

#2 Updated by Benjamin Dauvergne over 4 years ago

  • Priority changed from Normal to Bas

#3 Updated by Mikaël Ates over 3 years ago

  • Patch proposed set to No
  • Tracker changed from Bug to Development

Also available in: Atom PDF