I am running into the JIRA issue http://www.ja-sig.org/issues/browse/CAS-663. At the moment for our pilot implementation of Google Apps we have Shibboleth sitting in front of CAS to handle the SAML side of things. We are going live with our Google implementation on June 16th, and I was hoping to be able to remove Shib from the equation by that point. Is it possible to work around this issue by somehow configuring CAS to see several OUs in the same AD directory as separate directory servers? 90 percent of our users are in the 'Users' container. I would like to configure CAS to look there first, then fail over to the 2-3 other containers that have users. This would have to work for both authentication and attribute retrieval.
Thanks! - Isaac -- 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
