HP Web Jetadmin Software Uživatelský manuál stáhnout pdf (Strana 80)

passwords. Any user with access to devices and conguration features has delegated access to the Credential

Store.

Credentials Needed

When HP Web Jetadmin, during an action such as device conguration, encounters a device with a credential

such as SNMP Set Community Name, it follows a specic sequence. Here is a simplied example showing how

HP Web Jetadmin attempts to resolve a credential:

●

HP Web Jetadmin checks the Credential Store for a credential.

●

If a credential exists, HP Web Jetadmin attempts the conguration using the credential value.

If a credential does not exist, HP Web Jetadmin checks Global Credentials.

●

If the conguration is successful, the credential check is resolved and complete.

If it fails, HP Web Jetadmin checks Global Credentials.

During a user-attended conguration session, HP Web Jetadmin prompts for credentials. If the user does not

supply the credential or the session is not live, the device is agged as Credentials Required and listed in the

Credentials Required column that can be enabled in any device list (Columns for Device Lists on page 106). You

can right-click the device and add the needed credential to the system in order to resolve this state.

HP Jetdirect Device Password

HP Web Jetadmin enables device security by providing management over appropriate, device-based security

settings. The HP Jetdirect password that was used by HP Web Jetadmin in the past is a software security

solution and not a device-based security solution. That is, the password itself had to be recognized and

authenticated by earlier revisions of HP Web Jetadmin software. Other applications did not recognize this

password and did not force users to prove knowledge of the password.

As security features have become more sophisticated and device based security has improved, HP Web Jetadmin

developers have opted out of using the HP Jetdirect device password as a protective mechanism for device

authentication. Instead, HP recommends that you choose one of the following two recommendations providing

device security:

●

SNMP Set Community Name: Devices will not allow an SNMP Set from any application without the Set

Community Name correctly embedded in the SNMP packet. If the Set name in the packet is “public” and the

Set name on the device is “George”, the device will not accept or acknowledge the packet. Set Community

Names traverse the network in clear text and, therefore, can be “snied” or viewed by eavesdroppers. In

most environments, security provided a Set Community Name may provide adequate security.

●

SNMPv3: Devices congured via SNMPv3 oer signicant security benets. First, SNMPv3 congures a user

account and two pass-phrases onto the device that the user (or application) must authenticate. This blocks

unauthorized management of devices, and the account/pass-phrase details do not traverse the network in

clear text which makes it dicult for eavesdroppers to learn the “secrets”. Second, the communication

between the management application and the device is encrypted using the SNMP credentials so

information about the device is protected. SNMPv3 is recommended in security-sensitive environments.

Restricting Conguration by Device Group

Within the model of device credential delegation, restriction to specic device conguration can be further

dened in User Security using the Restriction type Groups (Restrict Roles to Device Groups on page 281).

54 Chapter 2 Introduction to HP Web Jetadmin ENWW

1 2 ... 75 76 77 78 79 80 81 82 83 84 85 ... 491 492

Komentáře k této Příručce

Žádné komentáře

HP Web Jetadmin Software Uživatelský manuál Strana 80

Komentáře k této Příručce

Související produkty a manuály pro Multifunkční zařízení HP Web Jetadmin Software