Web Site Login Password Protection


	Features \| How It Works \| Demo One \| Demo Two \| Download \| Hosting \| SSL Secure \| Contact Us

  Features

  How It Works

  Demo One

  Demo Two

  Download

  Hosting

  SSL Secure

  Contact Us

Website Login is server-side software that runs on the computer that hosts your web site. The software serves files and custom add-on extensions to authenticated users. Requests are made by placing HTML forms or links in your page. Website Login security cannot be bypassed since content is not publicly available. User credentials are verified each time a request is made.

website login authentication software diagram

What makes Website Login Software different from other technologies?

Website Login is fast, efficient and reliable because all client requests are handled by a single program instance in memory. And included in our software is a powerful BTree database that doesn't require any separate setup or integration. In addition to being professionally designed for concurrent read-write access-- this database has been benchmarked at an astounding 300 transactions per second with the Java HotSpot? Performance Engine 2.0

Set up protected areas during program execution and give your users access with a simple web-based administation menu. The demo html pages included with the install provide all of the html code you need to easily implement the login capabilities into your website. Create a folder for each protected area and add your site content. A protected area may have an index file and contain subfolders. Build links and forms to protected documents by specifying the servlet location, area name, and file name. Look at the demo html to use as an example.

Why are servlets better than CGI programs written in languages such as Perl and C?

Servlets are cross-platform:
Because servlets are written in Java, they can be used on multiple platforms without worrying about compatibility issues or recompilation. In addition by using servlets, you are not tying yourself to a single vendor solution.
Servlets are fast:
Standard CGI programs are slow because a new process must start up, run, and shutdown for every client request. For example: if a Perl cgi login program is being used by 25 users then the program has to be loaded into memory 25 times, executed, and shutdown- that's a lot of overhead.
Java servlets are fast because they are persistent. Our Website Login servlet loads only once and then services all 25 clients using multiple threads. It stays loaded in memory and waits for more requests and does not shut down for as long as the server is running.
Servlets are elegant:
Because Java was created from the start to be object oriented, programs written in that language tend be organized more effectively into easily manageable parts. This makes servlets easier to maintain and understand.
Servlets are secure:
Servlets are run in the Java security sandbox so can be insulated from disrupting the operating system or breaching security. Additionally, many security holes in traditional CGI languages result from those languages being weakly typed. Java's strong typing helps to ensure fewer accidental security mistakes.

What are the configurable parameters for Website Login Software?

AdminLocation - defines the location of administration area functions.

AdminPassword - defines the password that can access all of the administration functions.

CookieName - defines the name that cookies will be saved as. If not defined, "remember password" feature is disabled.

SessionName - defines the session name to differentiate users of multiple copies of the login servlet running concurrently.

DatabaseFolder - defines the folder containing the user and area databases.

AreaFolder - defines the folder out of the public domain that contains the protected areas

Template - specifies the name of a customizable html file so website login matches your site design

LogFile - specifies the file location of log file. A timestamp entry is made each time a user first logs in. If not defined then no log is written.

EmailNotify - Each time a user first logs in a notification email is sent

Extension1 - specifies an xml file defining Java add-on extension capabilities and associated menu. Define any number of extentions by using Extension1, Extension2, etc.

WelcomeTitle - specifies the title first shown on login page.

LoginMessage - specifies the subtitle first shown on member login page.

AdminMessage - specifies the message line first shown on admin login page.

MemberMessage - specifies the message line first shown on member login page.

DeniedTitle - specifies the title shown after a denied password on login page.

DeniedAdminMessage - specifies the message shown after a denied password on admin login page.

DeniedMessage - specifies the message shown after a denied password on member login page.

Why would I want to integrate Jakarta Tomcat with another webserver?

Other webservers like Apache webserver and Microsoft IIS deliver static pages faster and provide a vast array of features. Essentially-- if you don't have Jakarta Tomcat on port 80 and you don't integrate with another webserver then the tomcat port must be specified in links and forms. If you do integrate with another webserver then requests for Jakarta Tomcat are automatically forwarded through port 80 to Jakarta Tomcat running on a different port (usually 8080) by that webserver program.

How can Jakarta Tomcat be seemlessly integrated with Microsoft IIS on Windows 2000?

Install and configure Jakarta Tomcat as a system service started automatically at startup. For this example we assume the default installation location "C:\Program Files\WebsiteLogin\" was chosen.

Rename the file:

C:\Program Files\WebsiteLogin\jakarta-tomcat-3.2.4\conf\iis_redirect.reg-auto

to

C:\Program Files\WebsiteLogin\jakarta-tomcat-3.2.4\conf\iis_redirect.reg

and double click on it then click OK and a message states the information was added to the registry

-----

Start->Programs->Administrative Tools->Computer Management

In the left pane, Click on the small '+' next to "Services and Applications". Click on the small '+' next to "Internet Information Services". Right Click on the words "Default Web Site".

and select New->Virtual Directory

Type the name:

jakarta

click Next

Type the path as

C:\Program Files\WebsiteLogin\jakarta-tomcat-3.2.4\bin\win32\i386

click Next

Set Access Permissions:

check the box that says "execute" permission

uncheck the box next to "run scripts"

click Next

Program says Virtual Directory has been created successfully.

-----

Right Click again on the words "Default Web Site" in the left pane of "Computer Management" Window and select properties. Click on the "isapi filters" tab and click "Add..."

type Filter Name:

jakarta

and Executable

C:\Program Files\WebsiteLogin\jakarta-tomcat-3.2.4\bin\win32\i386\isapi_redirect.dll

Click OK

The jakarta filter name shows in the list.

Click OK

-----

Start->Programs->Administrative Tools->Services

Scroll down and Right click on "World Wide Web Publishing Service" and then select "Stop". The service is shutdown. Right Click again on "World Wide Web Publishing Service"and select "Start" and the service shows as started.

----

Right Click again on the words "Default Web Site" in the left pane of "Computer Management" Window and select properties. Click on the "isapi filters" tab and the jakarta filter now shows with a Green Up arrow for status and priority is listed as high.

Copy C:\Program Files\WebsiteLogin\websitelogin\Demo.html to wwwroot folder

Copy C:\Program Files\WebsiteLogin\websitelogin\Demo2.html to wwwroot folder

Goto the web address http://127.0.0.1/Demo.html or http://127.0.0.1/Demo2.html in browser for working demos

How are database operations performed from command line?

set INSTALL_PATH=C:\Program Files\WebsiteLogin

set CLASSPATH=%INSTALL_PATH%\websitelogin\lib\files.jar;%INSTALL_PATH%\websitelogin\lib\database.jar

set JAVA_EXE=%INSTALL_PATH%\java\bin\java.exe

set DATABASE=%INSTALL_PATH%\websitelogin\demo\database

"%JAVA_EXE%" CreateUserDatabase -user_database "%DATABASE%\UserIndex.ss"

"%JAVA_EXE%" AddUser -user_database "%DATABASE%\UserIndex.ss -username user1 -password passw -areas area1,area2,area3

"%JAVA_EXE%" DeleteUser -user_database "%DATABASE%\UserIndex.ss -username user1

"%JAVA_EXE%" ListUsers -user_database "%DATABASE%\UserIndex.ss"

"%JAVA_EXE%" CreateAreaDatabase -area_database "%DATABASE%\AreaIndex.ss"

"%JAVA_EXE%" AddArea -area_database "%DATABASE%\AreaIndex.ss" -area area1

"%JAVA_EXE%" DeleteArea -area_database "%DATABASE%\AreaIndex.ss" -area area1

"%JAVA_EXE%" DeleteArea -area_database "%DATABASE%\AreaIndex.ss" -area customer -user_database "%DATABASE%\UserIndex.ss"

"%JAVA_EXE%" ListAreas -area_database "%DATABASE%\AreaIndex.ss"

How can I run Java add-on classes that I build myself to extend the capabilities of Website Login?

Create an addon definition xml file such as youraddon1.xml... simplest case - one class. Initial parameters are defined first

OR you can nest DefineOption tags and create a simple selectable menu

<?xml version="1.0"?> <extension> <initParameter> <parameterName>ConfigFile</parameterName> <parameterValue>~/WEB-INF/config/storeparams.xml</parameterValue> </initParameter> <initParameter> <parameterName>DisableConfigFileChanges</parameterName> <parameterValue>false</parameterValue> </initParameter> <defineOption title="Your Addon 1"> <defineOption title="Menu Item 1"> <class>com.you.code.extensions.MenuFunctionOne</class> </defineOption> <defineOption title="Menu Item 2"> <class>com.you.code.extensions.MenuFunctionTwo</class> </defineOption> <defineOption title="Menu Item 3"> <defineOption title="Menu Item 4"> <class>com.you.code.extensions.YourAddonFour</class> </defineOption> <defineOption title="Menu Item 5"> <class>com.you.code.extensions.YourAddonFive</class> </defineOption> </defineOption> </defineOption> </extension>

Inside web.xml for website login add "Extension#" parameter(s) that points to that xml addon definition file

<init-param> <param-name>Extension1</param-name> <param-value>~/WEB-INF/config/extensions/youraddon1.xml</param-value> </init-param> <init-param> <param-name>Extension2</param-name> <param-value>~/WEB-INF/config/extensions/youraddon2.xml</param-value> </init-param> . . .

Create an area inside the defined area folder for the extension and give a user access to it with Admin Menu.

Create a file inside that folder called access.websitelogin and put the name of the add-on inside that file: youraddon1

Inside your HTML page, square brackets tells Website Login look for the addon file

Your classes must implement LoginExtension.java (below)

package com.gchase.loginutil; import javax.servlet.*; import javax.servlet.http.*; import java.io.PrintWriter; import java.util.Vector; public interface LoginExtension { public void init(Vector parameter_names, Vector parameter_values, String doc_root, ServletContext context); public void performTask(Vector parameter_names, Vector parameter_values, String path, String username, String password, String page_string, String function_parameter, ServletContext context, HttpServletRequest request, String area_name, String area_path, PrintWriter out); }