Authenticating To The Edge - Watchguard Firebox X15 User Manual

Required
The mobile user must use a virtual adapter to connect with the
MUVPN client.
5
You can also enter a WINS Server address and DNS Server
address. Type the server IP addresses in the related field.
For more information on configuring the Mobile User VPN client
computer, see Chapter 10, "Configuring the MUVPN Client."

Authenticating to the Edge

When you authenticate with the Edge, it automatically identifies
your Administrative Access level. If you select the Automatically
prompt for login on Web access option from Firebox Users > Set-
tings, users will see the login dialog box when they open their web
browser. If you select this option or not, you can always open the
authentication login dialog box with this procedure:
1
Open a web browser.
You can use Netscape Navigator or Microsoft Internet Explorer. It is
possible to use the Edge with other Web browsers that support Java
script, but we do not support them.
2
To connect to the System Status page, type https:// in the
browser address bar, and the IP address of the Edge trusted
interface.
The default URL is: https://192.168.111.1
3
A security dialog box appears. You must accept the warning
before you can continue.
If your web browser is configured to block pop-up windows, it is
possible that some dialog boxes used by the Edge will not appear.
This includes dialog boxes used by wizards, and the dialog box
used to log in to the Edge.
When you authenticate with the Edge, one of two screens appears.
A user with Read-Only or Full Administrative Access sees the Firebox
X Edge System Status page. A user with Administrative Access set to
None sees a dialog box with an authentication status message. This
dialog box is known as the Login Status dialog box.
If you are using local authentication, you must type your name as it
appears in the Firebox user list. If you use Active Directory or
another LDAP server for authentication through the Firebox X Edge,
you must include the domain name. For example, if the administra-
User Guide
About User Authentication
N
OTE
141