I don't see any password encoder configured. If you don't have one configured that means you're comparing the hashed password against your plain text password.
You can see from this line: https://github.com/Jasig/cas/blob/master/cas-server-support-jdbc/src/main/java/org/jasig/cas/adaptors/jdbc/QueryDatabaseAuthenticationHandler.java#L60 It does a comparison against the value returned (which in your case looks hashed based on the field name) On Mon, Jul 21, 2014 at 11:17 PM, jason <ja...@metroworks.co.jp> wrote: > Well thanks for the help; it's progress just to confirm that my config > seems okay. > > I feel like improper credentials to my database in the > deployerConfigContext.xml file should result in clear error messages in the > logs to the effect that the database connection is failing. > > Any developer on the project care to comment? Should I file an issue for > this? > > Similarly, as I've mentioned before, upping the log level to "DEBUG" > everywhere I can find still does not seem to give me any indication as to > why the authentication is failing. Does the database connection fail? > Does it fail to find the correct username? Does it find the username, but > not a password field? Does it find both those things, but then the > password fails to match? I have no idea. > -- > You are currently subscribed to cas-user@lists.jasig.org as: > scott.battag...@gmail.com > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > -- You are currently subscribed to cas-user@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
