When System Administration & Diagnostics connects to a system, it attempts to authenticate using various scripts that different systems recognize. See Adding Connections Manually for information for connecting to a system.
In all cases, DB Programming and other system management tools and utility options (see Launching Utilities) are enabled. When DB Programming or a utility is launched, access may be limited or you may be prompted for further authentication depending on how the connection settings are configured. The following table shows how the System Administration & Diagnostics application behaves when authentication is successful or failed.
Table: Authentication Results
|
Connect Response |
System Version |
Authentication Result |
Web Page and Diagnostics Allowed |
Information Bara |
System Monitoring Available |
|
Received |
4.0 or later |
Authenticated |
Yes |
Success (unless an unrelated warning exists) |
Yes |
|
No |
Warning |
No |
|||
|
Failedb |
N/A |
Failure |
No |
||
|
Pre-4.0 |
Authenticated |
N/A |
Warning |
No |
|
|
Not Receivedc |
Any |
N/A |
N/A |
Warning or Failure, depending on other conditions |
No |
a. See Information Bar Status Messages for a complete list of status messages in the Information bar.
b. When authentication fails, use the Edit connection button in the Information bar for quick access to edit the system account settings for the connection (see Adding/Editing Connections). When you update the account information and save the connection, as long as the automatic connect option is enabled, System Administration & Diagnostics immediately retries the connection using the new account information.
c. When the System Administration & Diagnostics application does not receive a connect response, you may consider any of the following situations: the host is not a 5000 CP, a connection setting is incorrect, the system’s Web server is not available, and so on.