Basic Authentication is always performed by the Web Server before allowing access - IOW, it logs you in then passes you the log in information. Basic Authentication provides the username and password actually in Base64 encoded form and you can decode that, but at that point you've already logged in.

There's no built in way - nor should there be on to use an existing table unless you use a specific technology that supports special authentication handling. The only way to override this sort of behavior is by using Server plug-ins (like filters in IIS)...

If you need to validate users from tables you will need to use form variables from HTML and pass the data over the wire via SSL. That's the only reliable way to do this.

+++ Rick ---




>I have a table (dbf file) which contains user names and passwords and other
>fields. I use SSL protocol in web server.
>
>I have found that http basics authentication info (user name and password) is not passed to my app from web server.
>
>I don't want to pass user name and password as
>hidden form variables or query string parameters: those can be read by
>intruder since pages are cached in a local disk.
>Also, I cannot use temporary cookie since this may be disabled.
>My app can read and delete users and this is difficult to syncronize
>this table with web server users table so I cannot use web server buil-in
>page based authentication.
>
>How to implement user authentication in this case ?