Just pushed a sample on that, here is the config with md5 and it works fine https://github.com/apache/tomee/commit/d995c944636bc9978633376ee6ec5ada4994dca9#diff-d326ee796fb18a217874b310e3433a55R71
can it be the database encoding which wouldnt use ISO88591? Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber <http://www.tomitribe.com> | JavaEE Factory <https://javaeefactory-rmannibucau.rhcloud.com> 2016-08-26 4:17 GMT+02:00 scaddenp <[email protected]>: > Thanks, now I am debugging fine. The problem is in > MessageDigestCredentialHandler. When the .match is called, algorithm is > null. RealmBase.setCredentialHandler is never called. > Clearly, the > <CredentialHandler > > className="org.apache.catalina.realm.MessageDigestCredentialHandler" > algorithm="MD5" saltLength="0" iterations="1"/> > in server.xml is not being picked up. I cant spot any typos here. It seems > to conform to the 8.5 documentation. > > While the digested password is being returned okay, I note that the > resource > is defined in context.xml, not in tomee.xml. I cant see how that could get > in the way however. > > > > -- > View this message in context: http://tomee-openejb.979440. > n4.nabble.com/Digest-changed-from-1-7-2-to-7-0-1-tp4679792p4679910.html > Sent from the TomEE Users mailing list archive at Nabble.com. >
