cas

I'm hoping some of you who have experiencing using CAS and CAS Attributes on UC Berkeley sites can help me with a couple questions about ideal setup:

I've got the modules set up and can see LDAP attributes, but there aren't any available CAS attributes. Is that normal? I'm using auth-test.berkeley.edu and ldap-test.berkeley.edu.

Also, what's the best way to deal with the fact that you don't always get an email address in the LDAP attributes? Do you just leave the user email field blank when new accounts are created? (Or maybe there's an email in my missing CAS attributes?)

Thanks!

Depois de fazer o upgrade para a versão 7.2, a autenticação via CAS começou a dar erro, mas ainda assim autentica o user. Só que, na página principal do site, publica a vermelho o seguinte:

"..Warning: DOMDocument::loadXML(): Input is not proper UTF-8, indicate encoding ! Bytes: 0xE3 0x6F 0x20 0x63 in Entity, line: 3 in domxml_open_mem() (line 72 of /usr/share/pear/CAS/domxml-php4-to-php5.php)..."

Alguém tem ideia de como se resolve isto? Fico a aguardar. Obrigado

Abraços

Fernando Alberto

Hi all,

Looking for some ideas on the right solution here. We are building several Drupal sites with a common user audience. These users also will be accessing Moodle content via hyperlinks from Drupal (i.e. we are not directly integrating Drupal and Moodle).

Looking for a centralized authentication server implementation that can:

<

ul>

Hi,

We're looking at SSO solutions to replace the system we currently use which was built in-house. Our requirements (for now) are:

• Works with Drupal
• Works with WordPress
• Works with custom PHP applications
• Supports LDAP, Kerberos and optionally SPNEGO
• Ideally Open Source
• High Availability

We've narrowed down our choices to four options:

• CAS
• CoSign
• OpenSSO
• Shibboleth