>From your logs it looks like egroupware thinks each request is a new session, and so is authenticating to CAS every time. Most apps set session Ids with a cookie, so you might want to look at what's happening on the browser side with Fiddler or HttpFox and see if you're sending a session cookie or not (or if egroupware is setting one). If the session cookie is not there, check your app's configuration. CAS itself looks fine.
Rich On 07/05/2011 05:24 AM, Fisher wrote: > Dear All, > > I having trouble to get working the CAS server in my environment. > > At firs my environment: > > - all the machines are OpenVZ containers > - all the machines behind nginx proxy > - https have been set up > > The CAS server itself seems working I can access it (https) and can > log in with username/password retrieved from LDAP. > > The application I wish to cassify is the egroupware, my browser tells > me it detects redirects which are will never ends. > > To reduce the post size I have put the cas debug into a pastebin: > http://pastebin.com/jPTSbY93 > > Also posted the cas server log: http://pastebin.com/CVpJBnz0 > > The only thing that confuses me the changing client address however I > believe it should not be problem. Please advice. > > Thank you for your help. > > > -- 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
