Typically, a lack of attributes when otherwise expected indicates that none were "released" to the app via the Services Management Tool (this of course assumes that you've confirmed that they are being properly retrieved).
On Wed, Sep 1, 2010 at 8:23 PM, Marvin Addison <[email protected]>wrote: > > <init-param> > > <param-name>service</param-name> > > > > <param-value> > http://myServer.myCompany.com:8080/TestApp1/sso/ProtectedServlet > </param-value> > > </init-param> > > Two things here: > > 1. I would avoid statically specifying the service parameter unless > you have a specific use case. The Java client can determine the > service dynamically at runtime, which is the default and typically > best configuration. > 2. You're using plan http. SSO will not work by default over http. > Additionally, and more to the point, I believe 3.4.2.1 specifically > restricts services to https. You should inspect the services > management console to ensure that your application is authorized to > communicate with CAS and that it is authorized to receive attributes. > > M > > -- > 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
