If you've configured the filters correctly, then you just use the standard Servlet calls:
i.e. request.getRemoteUser() or request.getPrincipal() Cheers, Scott On Mon, Jun 22, 2009 at 4:18 PM, Gerald D. Anderson <[email protected]> wrote: > Greetings all. > I am doing some work for a company that has a liferay portal that is > using CAS (3.3.2) for authentication. I have written a JBoss Seam (2.1.1) > app for said company and I need to authenticate to their CAS server. I've > downloaded cas-client-core-3.1.6.jar and have the filters configured (they > appear to be working) in web.xml. So far so good. > > However, now I've hit a complete and total brick wall. I can find ZERO > documentation on the java side of things for the ja-sig java client. I can > find 100 things on configuring sprint, web.xml, etc, but nothing on how to > validate the authentication from the java side. > > What I'm trying to do is modify my authenticator just to verify that the > current session has been authenticated correctly through CAS and get the > principal information (username is all I really care about). Then I hope to > load the seam entity for the user and throw it in the Seam identity. All of > this in a java class file (Seam component) if that's not clear. > > Could anybody please send me in the direction of documentation regarding > how to use the java client to verify/get this information? I'll take > example code, javadocs with some directional pointers, just about anything > at this point ; ) > > Thanks! > Gerald Anderson > > -- > 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
