This would allow users to login via their university account (like how Google/Kaltura login is handled). This would reduce people needing to maintain a second set of credentials.
If necessary could maintain old login flow for external people without a university account.
By attaching a uni username to each existing account, it could act as a "whitelist" on the site, to only permit certain usernames to login.
It should be pretty easy to fold in via django-cas-ng, I've just integrated it into a site I'm building for COM4521 (although it was only setup for https:// which added a little extra faff to my dev server).
It's necessary to request CAS registration from IT services, however that's simply a case of providing them the domain and asking (was handled in 24h).
This would allow users to login via their university account (like how Google/Kaltura login is handled). This would reduce people needing to maintain a second set of credentials.
If necessary could maintain old login flow for external people without a university account.
By attaching a uni username to each existing account, it could act as a "whitelist" on the site, to only permit certain usernames to login.
It should be pretty easy to fold in via django-cas-ng, I've just integrated it into a site I'm building for COM4521 (although it was only setup for
https://which added a little extra faff to my dev server).It's necessary to request CAS registration from IT services, however that's simply a case of providing them the domain and asking (was handled in 24h).