[JAMES-332] Support other digest algorithm (was: SHA hard coded in adduser)

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: 2.2.0
• Component/s: SpoolManager & Processors, UsersStore & UsersRepository
• Environment: FreeBSD, Sun JDK 1.4.2-p6, MySQL via. C-JDBC.
• Assignee: Norman Maurer
• Reporter: Brill Pappin
• Created: 05/Nov/04 03:05
• Updated: 09/May/22 02:10
• Resolved: 09/May/22 02:10

Description

It seems that JDBC is the default digest alg when creating users. this works fine when the use repository doesn't have to work with anything else, but MD5 is more common.

In my case, I'm using a custom configuration that allows me to use the same auth table for Tomcat and James. I think (though I haven't checked) that I can configure tomcat to use SHA, but I have a significan't amount of legacy data that uses MD5, whic is going to break thing.

As of now, my only option is to try and recompile James with MD5 as the default (and I havn't had much luck yet). Because of that, this ticket is marked as Critical.

Issue Links

• incorporates: JAMES-334 SHA hash incompatable with common generation methods
• is related to: JAMES-335 digest alg ignored wen using JDBC user repository