[ http://issues.apache.org/jira/browse/JAMES-332?page=all ]
Stefano Bagnara updated JAMES-332:
----------------------------------
Summary: Support other digest algorithm (was: SHA hard coded in
adduser) (was: SHA hard coded in adduser)
type: Improvement (was: Bug)
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.
was:
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.
Priority: Minor (was: Critical)
Cleaning JIRA: This is not a BUG but a request for an improvement.
I changed the topic and I consider it to include the other related reports.
Please look at the descriptions in the already resolved issues linked to this
issue.
> Support other digest algorithm (was: SHA hard coded in adduser)
> ---------------------------------------------------------------
>
> Key: JAMES-332
> URL: http://issues.apache.org/jira/browse/JAMES-332
> Project: James
> Type: Improvement
> Components: UsersStore & UsersRepository, SpoolManager & Processors
> Versions: 2.2.0
> Environment: FreeBSD, Sun JDK 1.4.2-p6, MySQL via. C-JDBC.
> Reporter: Brill Pappin
> Priority: Minor
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
