Prev   Next

Back to the top of the FAQ

Q. I want cookie based login with a form, not Basic Authentication with a pop-up dialog.

A. Cookie-based authentication allows you to make various extra settings, such as timeout.
Browsers that do not have cookies enabled will be denied access. See the dialog here: cookie.htm

Note, Windows 2003 requires version 6.0 and above for cookies to work correctly.

The Software comes with samples to help you get started with cookie authentication:
Look in the ASPocxSamples\CookieLogin-SiteWide subdirectory of the installation directory.
Map a virtual directory to this directory. Then use AuthentiX to protect the members sub-directory with cookie-based protection. See the dialogs above.

Note that if you are using per-directory cookie login, the urls that AuthentiX checks are case sensitive, make sure that links into the protected area are all lower case (or match the case of the directory you specified when setting up the cookie).

If you suspect the cookie is not being correctly passed to the server, setup cookie protection as normal, then place debug.asp (there are several of these in the samples directories) into the protected area. Then -remove- the protection in AuthentiX (you can just rename the directory in AuthentiX to keep your settings), and redirect to the debug.asp. This will show you what cookies have been set. Remember to View Source, because the angle brackets in the cookie value will be interpreted by the browser as failed html tags.

If you are having problems with your implementation of cookie-based protection, go back to ASPocxSamples\CookieLogin-SiteWide, and protect the members subdirectory.
This will work, then step forward to where you want to be.

Please do not call or email tech-support with a whole set of asp files you have created saying "it does not work - help". We are not equiped to handle this kind of enquiry unless it is on a consulting basis.

If you are having problems with your implementation of cookie-based protection, go back to ASPocxSamples\CookieLogin-SiteWide, and protect the members subdirectory.
This will work, then step forward to where you want to be.

If you are still having problems, and you are authenticating against an ODBC database, please supply the answers to the following questions:

  • Start with Basic Authentication and Internal database.
    Works? Yes or no.
  • Then Basic Authentication with ODBC database, Standard select statement.
    Works? Yes or no.
  • Then cookie Authentication with internal database, using the sample provided only, with no modifications.
    Works? Yes or no.
  • Then cookie Authentication with ODBC database, Standard select statement, using the sample provided only, with no modifications.
    Works? Yes or no.
  • Advanced Users only: If you are using stored procedures, or By COM, make sure you follow the instructions here regarding GetCrypt.
Start instead with the CookieLogin-SiteWide sample mentioned above.

Here is the online documentation for the OCX cookie methods:
http://www.flicks.com/authentix/authxref.htm
http://www.flicks.com/authentix/cookieSWValue.htm

If you are implementing cookie login at your ISP who supports AuthentiX, you will need to get the CookieLogin-SiteWide samples by downloading the free trial download, install it, and refer to the installed samples. Remember if you are using the samples on AuthentiX ISP version, you will need to change the line:
usingAuthentiXStandard = true
to usingAuthentiXStandard = false
If you are at an ISP, and you are administrating by Host-Header or directory, then you will also need to uncomment the line
protectedDomain = "hostheader.com"
and change the value appropriately. If you don't do this right, you will get lots of -3 errors.

If the remote admin just seems to hang, try the /aspadminisp/standardtext/ directory instead.

Back to the top of the FAQ

Prev   Next