> It may rely on a component you don't care about, but it's part of your > product as well.
I totally agree we should care about this, but it's really not a part of our product (Java CAS Client). You can use the Java client independently of Spring Security, and the CAS integration that's a part of Spring Security isn't related to the InMemoryDaoImpl component that is used in the case of your configuration. I'm doubtful that have enough weight to throw around in Spring Security to encourage those folks to change behavior like case sensitivity in general, but maybe we could help them see the light that things like this are really time wasters for deployers like you and the behavior should be better documented or configurable. 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
