Authentication Methods - Java Login
The WinGate Java logon applet is a multi-purpose tool for authenticating WinGate users. The applet is loaded by any web browser when ALL of the following are true:
- The web browser is set to connect to the Internet with the WinGate Proxy.
- The WWW Proxy Service is configured to Use Java Client authentication as required by policies (enable this with the checkbox on the General configuration of the WWW Service properties)
- The System or Service policies require that the User must be authenticated (this option is available by double-clicking a policy recipient e.g. Everybody)
Though the user must use a web browser to load the applet, this authentication works for WinGate Services other than the WWW. For example, you can configure the FTP Service to User must be authenticated.
To authenticate themselves, (if the WGIC is not running) the users simply start their web browser and logs into the Java Applet. Once the login is complete, the users can start the FTP client and will be authenticated.
Notes:
-
The Remote Control Service must be bound to the local LAN Interface (Internal adapter) for Java authentication to work.
- The Java Applet will only appear when a particular user requires a higher level of authentication for the request being made. For example, if you configure the WWW Proxy Service to User may be assumed then the applet will only be served to non-assumed users.
- The SOCKS Proxy Service will also serve the client if Refer HTTP requests to caching HTTP Server is enabled. (Socks Advanced Tab on the SOCKS Service properties).
- Java Login will not work when NT Authentication is used by WinGate (The Java Authentication will not be available in the WWW proxy when this is the case).
