Java client authentication

There are two methods of authentication in WinGate:

Administrators can log on with Gatekeeper to configure and monitor WinGate.

Users can authenticate thought their web browser by means of the java WinGate logon client.

To make use of the java logon client, select the ‘Use Java Client authentication’ option on the WWW Proxy. When a non-authenticated user attempts to use a web browser, a page will appear with the following text:

Wingate Logon

Please log on to WinGate now. You will automatically be logged off the system when you close down your web browser. You will require a Java enabled browser to complete the log on process.

Then this window appears with an appropriate user name:

Enter your User Name and Password in the spaces provided and click Logon.

When the status reads “Connected”, your browser will then receive the page you requested.

Points:

This is a Pro only feature.

If you have logged on with Gatekeeper, the client will not appear. However, if you are logged on with the client, you can still logon with Gatekeeper. Having two logins is not recommended.

The client will not appear if you do not require authentication.

Other services may require authentication, but only the WWW proxy can serve the client. (If this is the case, use a browser to log in first.)

The SOCKS server will serve the client if HTTP hand-over is enabled.

If you disallow non-authenticated users, the WWW will still serve the logon client. On WinGate installations that require authentication for access, simply start up your Web browser and log on with the client.

The logon client may act slightly differently in different browsers. Closing the browser always closes the client and logs off the user.