if i'm going to be using sha-1 for the encryption, do i just specify
digest=SHA, digest=SHA1, digest=SHA-1?
thanks,
joe
i'm talking about this part of configuration:
http://tomcat.apache.org/tomcat-6.0-doc/realm-howto.html
On Thu, Sep 18, 2008 at 3:18 PM, Christopher Schultz <
[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Joe,
>
> Joe A wrote:
>
i'm talking about the part of configuration that lets you choose specify how
the passwords are stored in the users table.
On Mon, Sep 22, 2008 at 2:27 PM, Christopher Schultz <
[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Joe,
>
>
2008 at 3:06 PM, Mark Thomas <[EMAIL PROTECTED]> wrote:
> Joe A wrote:
> > i'm talking about the part of configuration that lets you choose specify
> how
> > the passwords are stored in the users table.
>
> To repeat my previous answer, any digest that is supporte
is it really that hard to reply to a question without coming off as a
pompous ass?
On Mon, Sep 22, 2008 at 4:23 PM, André Warnier <[EMAIL PROTECTED]> wrote:
> Mark Thomas wrote:
> [...]
>
>> It took me less than a minute to find the JavaDoc for
>> java.security.MessageDigest
>>
>
> It's by saying
if i redeploy my webapp and try to access a protected page, it will show
the login
screen but after clicking login it just reloads the login page instead
of sending me to the protected page. if i reload the login page it will
give me access
to the page i wanted. if i fill in user/pass and hit lo
attribute of
the form tag. Tomcat will take control when it sees a client trying to
access a protected resource without a valid session and return the login
page. Your code doesn't have to ever do that.
--David
Joe A wrote:
> if i redeploy my webapp and try to access a protected p
