Giri, I have just solved the same issue. I did it by moving username and password into an LDAP store and letting LDAP handle auth for the web application and James.
Robert On Wed, Sep 25, 2013 at 2:08 PM, Girivaraprasad Nambari <[email protected]> wrote: > *NOTE: sorry for posting little bit off topic question. I thought some one > in this might have faced this requirement while using james. Any input > would be appreciated.* > > *------ > * > > ** > > We have web application where upon registration user will get email account > created on James server. > > For example, if user registered as IAMSAM with password SOMEPASS, our code > creates an emailID account with name *[email protected]* and *SOMEPASS* as > password. > > Right now we are storing passwords in database as hash/salt. > > The issue we are struggling address is, when user login & move to some page > where they can fetch emails from James, we can't pass "plain text" > password (because we are keeping salted password only) to authenticate. > Can someone please help with pointer for solution? > > I see one possible way is, use hash/salt password while creating email > account, but this may not work if user try to access his/her email account > from other clients like Mozilla Thunderbird. > > Any input would be appreciated. Thanks for your time and help. > > Thank you, > > Giri --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
