Gossamer Forum
Home : Products : Links 2.0 : Discussions :

user 2: password mismatch: .HTACCESS problem!

Quote Reply
user 2: password mismatch: .HTACCESS problem!
This is what I'm getting when I enter my user name and password.
I know I have .htaccess pointing to the right .htpasswd directory.

Because I get this when I enter a false username and password.
user false not found:
I've chmoded 777 on both directories and .ht files, didn't work. Maybe a different chmod but I don't think so!

AuthUserFile /my/correct/directory/.htpasswd
AuthType Basic
AuthName "My Name"

<Limit GET POST>
require user 1 2 myname
</Limit>

Tried:
require valid-user
without <Limit>


Need more tips,

TIA

[This message has been edited by wesley (edited October 14, 1999).]
Quote Reply
Re: user 2: password mismatch: .HTACCESS problem! In reply to
you are encrypting it with a correct key right?

i know salt and MM are keys availible to all servers.. but then some servers (hypermart) are limited to their own key.. HYPERMART=Cd

i have a salt encryptor that i made for someone to use here:

http://www.pdamania.com/encrypt.cgi

jerry
Quote Reply
Re: user 2: password mismatch: .HTACCESS problem! In reply to
Yes the passwords are encrypting but I'm not sure what you mean by 'with a correct key'.

uhm,
htpasswd .htpasswd username (Telnet)
is what I did.

More info:
using Apache Web Server 1.3.2
Sun Solaris 5.6

I've checked the Apache Web site documentation and the various sites suggested here but every variation I've tried doesn't work.

NEVERMIND!!!!

You're right about the encryption and incorrect key!
Right on.

Can you give me more details about this incorrect key so I can tell my idiot administrator that he has it set up wrong - Smile this has been frustrating me for quite some time now.

Thank You, Thank You, Thank You

WAIT!!!!!

Seems that the password once entered does not have to be re-entered when I tried for the username-password pop up window again.

Must make myself clear here. The user name and password only has to be entered once and then the directory is no longer password protected.

What's up with that?

[This message has been edited by wesley (edited October 14, 1999).]