Hi! Our company provides a software service (expense reports) to multiple customer organizations. We handle authentication several ways, and are adding CAS for a particular customer. The Java client looks to work well for this first customer, but we expect to have more CAS customers in the future. Each of these would have their own independent CAS server.
What's the right way to handle the situation where an application needs to authenticate using CAS, but the CAS server login URL can be different for each login attempt? We'd like to use the Java client if possible, with as few modifications as possible. But we don't want to add a different filter chain and login URL to web.xml for each customer; that doesn't scale acceptably. I'd thought of having the servlet and filters configured to handle a wildcarded URL, with the wildcarded part of the URI giving the customer name; that would let a modified filter look up the correct server login URL for this login. But the final keyword on doFilter() and non-dynamic server login URL combine to prevent us from extending the existing filters. Is there a better way than making our own slightly modified copy of them? I've looked over the docs and archives without finding a better answer. Leif Bennett Chrome River Technologies http://www.chromeriver.com -- 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
