OK, as I suspected it was an unrelated problem. I had left some @Provider functions in place from earlier experimenting - thinking that if I did not bind the associated type or Realm they would not be instantiated. Wrong!
It's all working quite well now. I did find one peculiarity - CAS sends my roles (from the "memberOf" attribute) over in lowercase. After not finding a setting to adjust this on the CAS side I just overrode the doGetAuthorization method in CasRealm and adjusted. On Tue, Jan 28, 2014 at 5:52 PM, rnmixon <[email protected]> wrote: > I've run into the situation where I need both Shiro CAS and Shiro Google > support. > > I've made an attempt to convert the buji-guice-demo to work with CAS > instead > of OAUTH. > > I created a InjectableCasRealm and InjectableCasFilter, but in my tests I > always end up going through BasicHttpAuthenticationFilter instead of the > "roles" filter. This is probably just a Shiro Guice configuration issue, > but > it's been beating up on me all day. > > If anybody could point out where I'm going wrong or suggest some other > things to try, it would be greatly appreciated. Here's my subclass of > > Thank you. > > > > > > -- > View this message in context: > http://shiro-user.582556.n2.nabble.com/shiro-guice-buji-tp7578225p7579595.html > Sent from the Shiro User mailing list archive at Nabble.com. > -- Richard Mixon Custom Computer Creations, L.L.C. mobile: (480) 577-6834 office: (480) 614-3442 email: [email protected] <mailto:[email protected]> Microsoft Partner ID: 1263725 The messages and documents transmitted with this notice contain confidential information belonging to the sender. If you are not the intended recipient of this information, you are hereby notified that any disclosure, copying, distribution or use of the information is strictly prohibited. If you have received this transmission in error, please notify the sender immediately.
