Tip:
Highlight text to annotate it
X
In this section, we will look at adding and configuring Orion® Web Console users.
First, we will look at adding new users
both as standalone Orion users and from Active Directory®
as individual or group accounts.
After that, we'll take a look at configuring user access
using permissions and account limitations to restrict access.
Finally, we will talk about customizing the user experience with tabs,
menu bars, and views.
User accounts can be added one of two ways.
One, either as a standalone Orion user
or two, from Active Directory.
Users are added by going to the Settings
in the upper right hand corner of the web console.
On the left you will find an Accounts area,
where you can add, edit, and manage user accounts.
From Manage Accounts, click "Add New Account."
There you can choose to create an Orion individual account,
a Windows® individual account from Active Directory,
or an Active Directory group account,
which adds an existing Active Directory group
so that any member of that group can log on to the Orion web console.
Adding a standalone user is very straightforward,
asking only for a user name, password, and password confirmation.
To add a Windows Active Directory user or group,
you will need to provide credentials for an administrative user
who has access to lists, groups, and accounts in Active Directory.
Once the search is complete, a list of users will be provided.
At that point, multiple users on the domain can be added as Orion users.
In this example, we will add a local Orion account with the user name Cheryl.
[Adding User Cheryl]
Once added, user access can be configured at a very granular level
controlling aspects such as what resources,
views, and menu bars that user has access to.
Limitations by node, vendor, and other parameters can be set as well.
Once a user is added, the next step is to configure their permissions
and access restrictions.
Again, under Managed Accounts select the user to edit.
In the Edit User screen the first section allows you to edit the following basic permissions:
Enable/Disable Accounts, Account Expiration, and Disable Session Timeout.
Turning this to yes will allow an account to remain logged on indefinitely,
even if the browser is closed.
Allow Administrator Rights allows admin rights to the Orion web console
such as the right to add or manage other user accounts.
This setting should be carefully considered
as administrator rights give the user full permissions
such as removing any account limitation that may be set on their account.
Allow Node Mangement Rights gives you the right
to edit, manage, add, or delete nodes.
Allow Account to Customize Views allows the user to customize
their own web console views, and changes to those views
will be visible to all accounts with access to that specific view.
Allow Account to Clear Events, Acknowledge Alerts and Syslogs
allows the user to manage alerts, events, and syslog messages through the web console.
Allow Browser Integration allows integrations of tools
on the client browser machine with the web page.
Alert Sound allows the user to select .wav file to be used when alert is fired.
Number of Items in Breadcrumb List
sets the number of breadcrumbs in the dropdown list.
So for Cheryl, we are going to give her node management
but not administrator and no view customization.
She has an Engineer's Toolset, so we will allow browser integration
and allow her to clear events and acknowledge alerts.
The next section allows you to configure account limitations.
Limitations are configured by clicking on the "Add Limitation" button.
This gives you a list of limitations to choose from.
Custom limitations can also be added
through the Account Limitation builder.
Once the limitation parameters are configured, it is applied to the user account.
The user experience can be configured by customizing views and menu bars.
Below the Account Limitations area both menu bars and views can be configured.
Menu bars and views are chosen from drop down menus
that contain not only the pre-configured objects
but also any custom components created.
If additional Orion modules such as SAM or NCM have been installed,
the views and menu bars for those modules are available for those as well.
In addition, the order in which the menu bar tabs appear on the web console
can be defined as well.
You can also configure a custom folder of reports the user has access to
by creating subfolders in the Reports directory
and assigning that folder to a user through this interface.
This provides the flexibility to give business users access to a subset of reports
they would be interested in without confusing them with too many options.
The last set of options in a user account is used to customize how devices
and monitored objects are viewed or hidden from the user.
By expanding the Orion General Settings
we see three Orion object views Nodes, Volumes, and Groups
and the dropdown that allows us to select custom views for these objects.
[©2012 SolarWinds Worldwide, LLC. All Rights Reserved.]