CAS is not looking at your handler for attributes; it will take a look at your resolver which right now has 3 hardcoded attributes, two of which can be released. (if you want the handler to take precedence, null out the resolver) If you are not getting those two, up the CAS logging to DEBUG and see what's coming out.
-----Original Message----- From: Richard Wiseman [mailto:[email protected]] Sent: Wednesday, August 6, 2014 12:58 AM To: [email protected] Subject: RE:[cas-user] Java-sourced custom attributes not being released There are lots of commented-out elements from my various attempts and I've scrubbed out the database details but here it is. Thanks! -- 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
