Events

Using Single Sign-On with GigaVUE H Series Nodes

GigaVUE-FM supports single sign-on authentication with H Series nodes running v3.0.05 and later. When this feature is configured properly, you can drill directly to an GigaVUE H Series node’s web-based interface (H-VUE) without having to enter login credentials – the credentials used in GigaVUE-FM are automatically passed to the managed H Series node and used to start the H-VUE session.

GigaVUE-FM users are mapped to local accounts differently depending on the configuration of the following aaa authorization settings on the H Series node:

Argument

Description

map order {remote-only,remote-first,local-only}

Specifies how drill-downs from GigaVUE-FM are mapped to local accounts

remote-first – Externally authenticated logins are mapped in the following order:
a. Mapped to the matching local account name, if present.
b. If there is no matching local account, the account name specified by the map default-user argument, below, is used. By default, default-user is set to the provided operator account.

This is the default behavior.

remote-only – Externally authenticated logins are mapped in the following order:
a. Mapped to the matching local account name, if present.
b. If there is no matching local user account, no further mapping is attempted.
local-only – All externally authenticated logins are mapped to the user specified by the aaa authorization map default-user <user name> command.

map default-user <user>

Specifies the account to which externally authenticated logins are mapped when map order is set to remote-first (if there is no matching local account) or local-only.

The default-user is set to operator by default. However, the preconfigured operator account is locked out by default because it does not have a password assigned. You must assign a password to the operator account for single sign-on to work successfully when using the default settings on the H Series node (remote-first enabled and default-user set to operator). The example below shows how to do this.

The following example shows an example of how to enable single sign-on from GigaVUE-FM to a managed H Series node:

Set a Password for the operator Account

1Start by checking the AAA settings in place on the H Series node with the show aaa command, as follows:

As you can see in the highlighted section above, the Default User is currently set to the operator account. This is the default setting on an H Series node.

2Next, check the status of the operator account with the show usernames account, as shown below:

1. As you can see in the highlighted section above, the operator account is currently locked out. To ensure that single sign-on works successfully, assign a password to the operator account to unlock/enable it. The example below shows how to assign a username and then check the status of the account:

Assign Roles to the operator Account

3Next, assign the operator account one or more roles to grant privileges on the H Series node. The following commands assign the Default role to the operator account and verify the results:

4At this point, single sign-on from the GigaVUE-FM installation managing this H Series node will work successfully. As an example, drill down to an H Series node’s H-VUE interface by selecting an entry in GigaVUE-FM’s Administer Physical Nodes page and clicking the Device Login button:

Notes and Rules for Single Sign-On Authentication

Keep in mind the following notes and rules when using the single sign-on feature from GigaVUE-FM to a managed H Series node:

Single sign-on is only supported for H Series nodes running v3.0.05 and later. It is not supported for earlier releases or for G Series nodes at all.
Single sign-on is supported for both standalone and clustered H Series nodes.
Single sign-on is supported for all combinations of remote and local authentication between GigaVUE-FM and the managed H Series node. For example:
Both GigaVUE-FM and the H Series node use remote authentication.
Both GigaVUE-FM and the H Series node use local authentication.
GigaVUE-FM uses remote authentication and the H Series node uses local authentication.
GigaVUE-FM uses local authentication and the H Series node uses remote authentication.

GigaVUE-FM keeps track of all events that occur in the system. The events lists all notifiable events that have occurred in the physical, virtual, and cloud. A variety of filters are also available to filter what events are displayed on the page.

This chapter covers the following topics:

Overview of Events
Filter Events
Archive or Purge Event Records