Thanks for the info William. I am integrating Drupal with CAS as well. How did you handle the in-line login? i.e. customer would enter their username and password, hit submit and have those credentials validated via CAS. Or are you simply doing a redirect to the CAS login page and ignoring the inline login?
-----Original Message----- From: William G. Thompson, Jr. [mailto:[email protected]] Sent: Friday, November 16, 2012 5:33 AM To: [email protected] Subject: [cas-user] CAS, Drupal, and Proxy Tickets Folks, I recently have been working with a client that is building a Drupal based enterprise portal (i.e. WebSSO, Role-based Content, Preview "portlets", etc...essentially a PHP based uPortal). And it turns out that Drupal supports Proxy Tickets via phpCAS integration. Once phpCAS with CAS2.0 protocol was turned on, the following PHP code was able to get content from CAS protected services: require_once drupal_get_path('module', 'cas') . '/CAS/CAS.php'; require_once drupal_get_path('module', 'cas') . '/cas.module'; cas_phpcas_init(); phpCAS::forceAuthentication(); $service = phpCAS::getProxiedService(PHPCAS_PROXIED_SERVICE_HTTP_GET); $service->setUrl('https://example.org/example_service.php'); $service->send(); return $service->getResponseBody(); Hopefully this is useful to others... Best, Bill -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
