To start working with Finder, first authenticate as a valid user. Take advantage of single sign-on solutions if your administrator has enabled either SAML authentication or Windows authentication of users. Otherwise, if plain authentication via Active Directory is available in your setup, log in with your Windows credentials. Alternatively, if no external authentication mechanism is available, use the credentials of your own dedicated Nexthink account.

The login process starts by connecting Finder to Portal. From Portal, Finder first retrieves the list of available Engines within your view domain and finally connects to the Engine of your choice. Once connected, Finder has access to the data stored both in the Engine and in the centralized content manager of Portal; letting you visualize, organize, and query end-user data in a variety of ways.

Quick connect

When you run Finder for the first time, the login dialog appears in Quick connect mode, as indicated by its title at the top left corner of the dialog. Quick connect mode lets you specify all the necessary credentials to connect to any Portal. To log in to Finder in Quick connect mode:

  1. Fill in the Host : Port field with the DNS name or IP address of Portal to which you want to connect, optionally followed by a colon and the port number where Portal is listening for connections (by default, 443).

  2. Depending on the authentication mechanisms available, choose one of the following:

    • If your administrator has enabled either SAML or Windows authentication of users, tick the box Use single sign-on.

    • If only internal or plain Active Directory authentication are available, enter your credentials manually:

      1. Type in your Username, which is the name of the user as registered in Portal.

      2. Type in your Password.

  3. Optional: Check the option Remember me to have the Host : Port and Username fields prefilled with the same data that you’ve just typed for the next time that you log in to Finder from the same computer. The next login, you will just have to retype your password (if not externally managed).

  4. Optional: Check the option Sign me in automatically for the login dialog to remember your password as well and skip the login step altogether the next time that you run Finder from the same computer. Checking this option implies that the previous Remember me option is also checked. Administrators can disable this option.

  5. Click Connect.

    • If SAML authentication is enabled and you have not logged in to your corporate account yet, Finder will open your corporate login page on your default web browser. Log in with your corporate account as usual.

  6. If more than one Engine within your view domain is available in Portal, a list with all connected Engines shows up in the dialog Engine selection:

    • Click the name of an Engine to connect to it.

    • Click the star to the right of the name of an Engine to make that Engine your favorite. The next time that you log in to Finder from the same computer, the step to select the Engine is skipped and you connect directly to your favorite Engine. You can later change your favorite Engine once you have logged in.

If Finder cannot connect to Portal or to the selected Engine, it aborts the login process and displays an error message with the reason for the failure. For warnings related to security certificates during the connection, see the section on certificate issues below.

Creating a session

In a multi-user or multi-Appliance environment (e.g. an environment with test and production Appliances), you may have to log in to Finder with distinct user accounts and connect to different Appliances from a single post. In these cases, to save you from typing the credentials every time you have to log in to a different Appliance, store the credentials for distinct users and associated Appliances into sessions. Later, log in to Finder faster by accessing your stored sessions.

To create a new session in the login dialog:

  1. Click the +New button found at the top right corner of the login dialog. The login dialog turns into session creation mode, copying the information that you typed previously in Quick connect mode, if any, or from a previously selected session into the fields Host : Port and Username of the new session. Note that sessions do not store passwords by default. You can later specify to remember your password if you frequently use the same session.

  2. Type in the DNS name or IP address of Portal appliance, followed by a colon and the port number where Portal is listening for connections in the field Host : Port. You can keep the copied value, if any.

  3. Type the name of the user to store in the session in the field Username. Again, you can keep the copied value, if the name of the user is not empty.

  4. Optional: Change the name of the session that is displayed at the top of the dialog by clicking on it and typing an alternative name. By default, the name of the session is built from the name of the user and Portal appliance in the form: Username on Host : Port.

  5. Optional: If the system supports either SAML or Windows authentication, tick the box Use single sign-on and Finder will let the external authentication mechanism manage the username and password. When using SAML or Windows authentication, specify a proper DNS name for Portal (not an IP address) under Host:Port.

  6. Click Create to save the session. The login dialog will now switch to session mode.

Note that sessions are created locally in your instance of Finder. Therefore, the sessions that you create in one computer are not automatically available when you try to log in to Finder from another computer.

Using a session to log in

Once you have created one or more sessions, you can use them to quickly log in to different Engines. You only have to select the appropriate session and, eventually, enter your password. To log in from a saved session from the login dialog:

  1. Click the down arrow in the top left tab of the login dialog, to the right of its title. A drop down list appears with the names of the saved sessions and the Quick connect option at the top.

  2. Select one of the saved sessions. The user and Engine information stored in the session are displayed in the dialog. If you select Quick connect instead, you will go back to Quick connect mode. Read the previous section on using the login dialog in Quick connect mode.

  3. Type in your password, if needed (not needed if you have previously told Finder to remember or if using SAML or Windows authentication).

  4. Optional: To store your password with the session information, check the option Remember password.

  5. Optional: Check the option Sign me automatically to skip the login step altogether and start the connection to the Engine of the selected session as soon as you open Finder. This option requires the Remember password option to be checked.

  6. Click Connect or press Enter and Finder starts to establish a connection to the chosen Portal.

  7. If more than one Engine within your view domain is available in Portal, a list with all connected Engines shows up in the dialog Engine selection:

    • Click the name of an Engine to connect to it.

    • Click the star to the right of the name of an Engine to make that Engine your favorite. The next time that you log in to Finder from the same computer, the step to select the Engine is skipped and you connect directly to your favorite Engine. You can change your favorite Engine later, once you have logged in.

If Finder cannot connect to Portal or to the selected Engine, it aborts the login process and displays an error message with the reason for the failure. For warnings related to security certificates during the connection, see the section on certificate issues below.

Editing a session

If one of your saved sessions has wrong data or there was a change in user or Appliance settings, you may want to edit the session. To edit the values stored in a session:

  1. Click the down arrow placed in the top left tab of the login dialog (to the right of the title) and select the session that you want to edit from the drop down list.

  2. Click the Edit button that you find at the top right corner of the login dialog. You will enter session edition mode.

  3. Edit the fields UsernameHost : Port and the name of the session in the same way as when you created the session (see previous section).

  4. Click Save to save your changes and go back to session mode.

Deleting a session

When you do not need a session anymore, remove it from your list of sessions. To delete a session from the login dialog:

  1. Click the down arrow placed in the top left tab of the login dialog (to the right of the title) and select the session that you want to delete from the drop down list.

  2. Click the Delete button that you find at the top right corner of the login dialog. A dialog appears asking you for confirmation on deleting the session.

  3. Click Yes to confirm that you really want to delete the session. The login dialog removes the session from the list and goes back to Quick connect mode.

Certificate issues

While connecting to Portal or to the Engine of your choice, Finder may display a warning message about security certificates on a dialog with the title:

There is a problem with Portal / Engine security certificate

Security certificates ensure that the connections among Nexthink components are safe. A problem with the certificates implies that there is a potential risk of impersonation. In particular, if you use the default self-signed certificates from Nexthink (or any other certificate not signed by a trusted CA), you can read the following message in the dialog:

The security certificate of Nexthink Portal / Engine could not be validated.

If you are testing the solution or you are sure that the certificate is correct:

  1. Optional: Click Show certificate to display detailed information about the current certificate.

  2. Optional: Tick the option Do not notify me again for this certificate if you want to accept the current certificate as valid and avoid the warning in subsequent logons.

  3. Click Continue anyway to go on with the login process despite the warning message.

Otherwise, contact your administrator for replacing the certificates. Log in only after your administrator has finished installing the new security certificates.


RELATED TASKS

RELATED REFERENCE