Middlebury

CASifying Moodle

Revision as of 15:06, 10 August 2009 by Adam Franco (talk | contribs) (New page: {{stub}} = Default CAS Plugin = The latest version of Moodle, 1.9, comes packaged with an authentication plugin for CAS. This authentication plugin should work for connecting Moodle to M...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Default CAS Plugin

The latest version of Moodle, 1.9, comes packaged with an authentication plugin for CAS. This authentication plugin should work for connecting Moodle to Middlebury's CAS server, but relies on an LDAP server for attribute lookup. While not ideal, this configuration should work with a few caveats that are listed in our CAS documentation.

Using the default CAS plugin rather than LDAP directly has the following advantages:

  • Moodle will use the same 'web-id' for uniquely identifying users
  • Users will not have to enter their credentials again if they have already logged into another application via CAS.

Configuration in Moodle

After enabling the CAS module, use the following configuration settings:

CAS server configuration

Setting
Value
Hostname
login.middlebury.edu
Base URI
cas/
Port
443
Version
2,0
Proxy mode
No
Logout CAS
Optional
Multi-authentication
Optional

LDAP server configuration

Setting
Value
Host URL
ldap://middlebury.edu
Version
 ?
LDAP Encoding
 ?

Bind settings

Setting Value

User lookup settings

Setting Value

Course creator

Setting Value

Cron synchronization script

Setting Value

Data mapping

Setting Value


Custom CAS Plugin with Attribute Support

We plan to create a customized CAS plugin that makes use of the user attributes returned in the CAS response. This page will be updated once such a custom plugin has been developed.

Using a custom CAS plugin has the following advantages over the default CAS plugin:

  • When implemented, visitor accounts will be available in Moodle
  • A full list of groups (including parent groups) are available