Auto Configuration - GE Optima XR220amx Operator's Manual

DRAFT
server cannot be reached. Note that hashed passwords are cached, the actual password is not
cached.
x
Enterprise Authentication Latency (Seconds) - The amount of time (in seconds) that the EA3 login pro-
cess should wait for a response from the Enterprise directory server. Often times, there is a network
latency when connecting to servers, and it will be different on different network configurations. If the
amount of time is reached without a response from the directory server, the EA3 login process will
return a failed login. A value of 5 seconds should be enough time to allow a properly configured direc-
tory server to respond, without being too much of an annoyance to the user if the directory server is
down (i.e. they will only have to wait at a maximum 5 seconds for the login attempt to return).
x
Applying configuration changes on the Enterprise tab top box are the same as mentioned before for
the Application tab. Use the Apply Configuration button to commit changes, and the Restore Config-
uration button to undo any changes that have not been saved yet. If there are any errors, you will get
a popup box describing the error.
x
Additionally, the actual connection to the Enterprise directory server can be made on this tab. You will
be modifying properties in the lower two boxes of the Enterprise tab

Auto Configuration

1. Press [Auto-detect Server Name].
x
This attempts to lookup the name of Server Name of the directory server.
x
In some environments, EA3 can try to auto-detect the Enterprise Directory Server. This will only work
in some environments (i.e. where DNS allows service lookups). This is just a convenience feature, and
will sometimes return with an alert that the auto-detect could not find the server. It is not an error if
that message is displayed, simply continue with these steps to configure the Server.
2. Enter the Server Name or IP address of the Enterprise directory server that EA3 should connect to, in
the Server Configuration box.
Note: The system must be able to resolve any IP address or server name. This means the system must
either have DNS enabled or the system must have static information in a hosts file (i.e. /etc/hosts).
3. Choose the Authentication type that the directory server supports.
x If it is a Microsoft Active Directory Server, most likely you need to choose Kerberos. If it is a Novell
eDirectory Server, most likely you need to choose LDAP If you do not know, check with the owner of
the directory server for information.
x If the enterprise server supports SSL connections, check the 'Use SSL' checkbox.
Note: If you use LDAP authentication without SSL, passwords will be sent in the clear. This is not recom-
mended, and the client is alerted if they attempt to configure this way. With kerberos and non-
SSL, the authentication is encrypted, but the LDAP traffic is not.
4. Press [Test Connection].
x This tests to see if the machine can connect to the directory server. If the connection is successful,
you will see a label with a 'CONNECTION OK' text next to the Test Connection button.
x If the connection is not successful, you will see a label with a 'CONNECTION BAD' text next to the
Test Connection button.
x If the connection is bad, then there is a problem connecting to the directory server.
Optima XR220amx X-Ray System
Operator Manual
CTRL+SHIFT+F to search using Search Index (faster)
54400222-1EN Rev 1 DRAFT 11092010
© 2010 General Electric Company. All rights reserved.
REVIEW COPY
Appendix A: Login Administration
A-20