localhost
admin
My account
Create content
Administer
Content management
Site building
Site configuration
User management
Access rules
CAS settings
Permissions
Roles
User settings
Users
Reports
Help
Log out
Home
›
Administer
›
User management
CAS settings
CAS server settings
CAS version:
1.0
2.0
CAS server:
Location of CAS authentication service.
CAS port:
443 is the standard ssl port. 8443 is the standard non-root port for Tomcat.
CAS URI:
If CAS is not at the root of the host, include a URI (e.g., /cas).
CAS PEM certificate verification:
Do not verify the certificate
Verify the server using PEM cerificate
Verify the Certificate Authority using PEM certificate
CAS PEM Certificate (phpCAS 0.6 or greater):
With client version 0.6 or greater this is the certificate for validating cas or the cas CA as appropriate.
User account settings
Is Drupal also the CAS user repository?
In most cases, the answer will be no; an LDAP repository will be the source of CAS users. But in some cases, the Drupal user database could be used as the central user store for single sign-on. If this is the case, select this option.
If Drupal is not the user repository, should cas highjack users with the same name?
If you have pre-created regular accounts in cas that you want converted to mapped accounts, check this box. Otherwise CAS will likely throw duplicate key violation errors on new users.
Should Drupal user accounts be automatically created?
If a CAS user logs in, his Drupal account will automatically be created. If you don't check this option, you will have to pre-create accounts for the users you want to allow.
Email Domain:
Append this domain name to each new user in order generate his email address.
Users canot change email address
Hide email address field on the edit user form.
Users canot change password
Hide password field on the edit user form.
Auto-assign users to the role(s):
authenticated user
This value can be used to establish a role automatically for all CAS users. As an example, if you are also using the simple_ldap module, you can use this role to establish a tie between CAS and LDAP-populated data. i.e. Users with the role of 'cas:user' should have their LDAP data updated automatically.
Redirection settings
Require CAS login for:
specific pages
all pages except specific pages
Specific pages:
node
Enter one page per line as Drupal paths. The '*' character is a wildcard. Example paths are '
blog
' for the blog page and '
blog/*
' for every personal blog. '
<front>
' is the front page.
Force redirection on initial login
Activate this option if you want a user to be directed to the following page after their first CAS login.
Initial login landing page:
Drupal path or URL. An example path is '
blog
' for the blog page. '<front>' is the front page. An example URL is '
http://www.example.com
'.
Successful login message:
The message displayed to a user when he successfully logs in via CAS. You may specify '%cas_username', the username of the user.
Redirect user on logout
Activate this option if you want a user to be directed to the following page after logging out of CAS. The logout destination must be specified below.
Logout destination:
URL. An example URL is '
http://www.example.com
'.
Miscellaneous settings
Change password URL:
The URL users should use for changing their password. Leave blank to use the standard Drupal page.
Registration URL:
The URL users should use for changing registering. Leave blank to use the standard Drupal page.
LDAP settings
Should we extract the user email from an LDAP directory?
Activate this option if you want to extract the user email from an LDAP directory.
Ldapauth module must be enabled and configured
.
Email attribute:
LDAP entry attribute containing the email address.
Should we extract user groups from an LDAP directory?
Activate this option if you want to extract the user groups from an LDAP directory.
Ldapgroups module must be enabled and configured
.