Logging on

The Please Login dialog box opens if you are not already logged on to the system as administrator, or if your log-in credentials are not cached.

Note: The User Name, Certificate Path, and Private Key Path
  1. Click Advanced to show the Certificate Path and Private Key Path fields.
  2. Ensure that the User Name fields automatically store the settings from the most recent log-in operation. Change these settings as required. field contains administrator. This is the user name that is defined for the security administrator during system installation.
  3. Ensure that the Certificate Path fields automatically store the field identifies the appropriate certificate file. This file is always in the %user folder%/.clide/certs subdirectory of the directory where the system is installed, and it always has the file name administrator-cert.der.
  4. Ensure that Private Key Path identifies the appropriate certificate key file. This file is also in the %user folder%/.clide/certs subdirectory of the directory where the system is installed, and it has the file name enc-administrator-key.der.
  5. Specify the password for the administrator user ID in the Password field.
    The button next to the Password field opens a dialog box for changing the password.

    If you plan to use another dialog box, or if you plan to use the Certificate Manager more than once, then select Use Credential Cache. This automatically applies the log-in information throughout the current session.

  6. Click Advanced to expand the dialog box to show the Certificate Path and Private Key Path fields.
    Note:  If Use Credential Cache is not selected, then you must log in manually each time you start a system dialog box.
  7. Click Apply. This loads the Certificate Manager.
  8. Click Advanced to expand the dialog box to show the Certificate Path and Private Key Path fields.
  9. Click Apply on the Login dialog box. This performs these tasks:
    • Checks the certificate and private key in the client.
    • Checks that the certificate on the server side is up to date. If it is, then the new certificate and the corresponding private key, if it exists on the server, are downloaded from the server to the client.
    • Checks if the private key can be uploaded to the server side.

      If it can, then the private key and the corresponding certificate are uploaded from the client to the server.

    • Uploads or downloads the certificate and private key based on the above checks.
    • Finishes the log-in when the certificate and private key are ready.