サポートと今すぐチャット
サポートとのチャット

KACE Systems Management Appliance 14.1 Common Documents - KACE Service Desk Administrator Guide

About the KACE Service Desk Getting started
Configuring the appliance
Requirements and specifications Power-on the appliance and log in to the Administrator Console Access the Command Line Console Tracking configuration changes Configuring System-level and Admin-level General Settings Configure appliance date and time settings Managing user notifications Enable Two-Factor Authentication for all users Verifying port settings, NTP service, and website access Configuring network and security settings Configuring session timeout and auto-refresh settings Configuring locale settings Configuring the default theme Configure data sharing preferences About DIACAP compliance requirements Configuring Mobile Device Access Enable fast switching for organizations and linked appliances Linking Quest KACE appliances Configuring history settings Configuring Content Security Policy
Setting up and using labels to manage groups of items Configuring user accounts, LDAP authentication, and SSO Deploying the KACE Agent to managed devices Using Replication Shares Managing credentials Configuring assets
About the Asset Management component Using the Asset Management Dashboard About managing assets Adding and customizing Asset Types and maintaining asset information Managing Software assets Managing physical and logical assets Maintaining and using manual asset information Managing locations Managing contracts Managing licenses Managing purchase records
Setting up License Compliance Managing License Compliance Setting up Service Desk Configure the Cache Lifetime for Service Desk widgets Creating and managing organizations Importing and exporting appliance resources
Managing inventory
Using the Inventory Dashboard Using Device Discovery Managing device inventory
About managing devices Features available for each device management method About inventory information Tracking changes to inventory settings Managing inventory information Finding and managing devices Registering KACE Agent with the appliance Provisioning the KACE Agent Manually deploying the KACE Agent Using Agentless management Adding devices manually in the Administrator Console or by using the API Forcing inventory updates About Remote Control Managing MIA devices Obtaining Dell warranty information
Managing applications on the Software page Managing Software Catalog inventory
About the Software Catalog Viewing Software Catalog information Adding applications to the Software Catalog Managing License assets for Software Catalog applications Associate Managed Installations with Cataloged Software Using software metering Using Application Control Update or reinstall the Software Catalog
Managing process, startup program, and service inventory Writing custom inventory rules
Deploying packages to managed devices
Distributing software and using Wake-on-LAN Broadcasting alerts to managed devices Running scripts on managed devices Using Task Chains
Patching devices and maintaining security
Using the Security Dashboard About patch management Subscribing to and downloading patches Creating and managing patch schedules Managing patch inventory Managing Windows Feature Updates Managing Dell devices and updates Managing Linux package upgrades Manage quarantined file attachments
Using reports and scheduling notifications Monitoring devices
Getting started with monitoring Working with monitoring profiles Managing monitoring for devices Working with alerts
Using the Service Desk
Configuring Service Desk Using the Service Desk Dashboard Managing Service Desk tickets, processes, and reports
Overview of Service Desk ticket lifecycle Creating tickets from the Administrator Console and User Console Creating and managing tickets by email Viewing tickets and managing comments, work, and attachments Merging tickets Using the ticket escalation process Using Service Desk processes Using Ticket Rules Run Service Desk reports Archiving, restoring, and deleting tickets Managing ticket deletion
Managing Service Desk ticket queues About User Downloads and Knowledge Base articles Customizing Service Desk ticket settings Configuring SMTP email servers
Maintenance and troubleshooting
Maintaining the appliance Troubleshooting the appliance
Appendixes Glossary About us Legal notices

Using an LDAP server for user authentication

Using an LDAP server for user authentication

About the login account on your LDAP server
Configure and test LDAP user authentication

User authentication can be done locally, using accounts created on the appliance, or externally, using an LDAP server.

If you use external LDAP server authentication, the appliance accesses a directory service to authenticate users. This allows users to log in to the appliance Administrator Console, User Console, or System Administration Console using their domain username and password.

For information about adding user accounts to the appliance for local user authentication, see:

•
About user accounts and user authentication
•
Managing user accounts for organizations

About the login account on your LDAP server

About the login account on your LDAP server

To set up LDAP user authentication, you need to create a login account for the appliance on your LDAP server. The appliance uses this account to read and import user information from the LDAP server.

The account needs read-only access to the Search Base DN field on the LDAP server. The account does not need write access, because the appliance does not write to the LDAP server.

In addition, the account must have a password that never expires. Because the password never expires, make sure it is very secure. The user can change the password (that complies with the appropriate security requirements), however, the password must be updated on the appliance. You can give the account a username, such as KACE_Login, or you can attempt to connect to the LDAP server using an anonymous bind.

Configure and test LDAP user authentication

Configure and test LDAP user authentication

You can configure and test connections from the appliance to an external LDAP server.

1.
Do one of the following:
◦
Log in to the appliance Administrator Console, https://appliance_hostname/admin. Or, if Show organization menu in admin header is enabled in the appliance General Settings, select an organization in the drop-down list in the top-right corner of the page next to the login information.
◦
Log in to the appliance System Administration Console, https://appliance_hostname/system, or select System from the drop-down list in the top-right corner of the page.
The Dashboard or System Dashboard page appears.
2.
Go to the Admin-level or System-Level Authentication Settings page:
a.
On the left navigation bar, click Settings, then click Control Panel.
b.
On the Control Panel, in the User Authentication section. click Configure Trust with LDAP (Administrator Console only), or Configure Trust with LDAP (System Administration Console only).
3.
If you want to disable the local admin account, and you are logged in as an administrative-level user through LDAP or SAML, select Configure Trust with LDAP.
Disabling the built-in admin account does not affect a tether used by KACE Support, when required. For more information about this feature, see Enable a tether to Quest KACE Support.
4.
Select the LDAP Authentication option:

Option

Description

Local Authentication

Enable local authentication (the default). If local authentication is enabled, the password is authenticated against the existing entries in the local database at Settings > Users.

LDAP Authentication

Enable external user authentication using an LDAP server or Active Directory server.

If LDAP Authentication is enabled, the password is authenticated against the external LDAP server.

For assistance with authentication, contact Quest Support at https://support.quest.com/contact-support.

5.
Click the buttons next to the server names to perform the following actions:

Button

Action

Schedule a user import for the server.

Modify the server definition. For information about the fields in this section, see Table 5.

Remove the server.

Change the order of the server in the list of servers.

6.
Optional: Click New to add an LDAP server. You can have more than one LDAP server configured.
* 
NOTE: All servers must have a valid IP address or hostname. Otherwise, the operation times out, which results in login delays when using LDAP authentication.
7.
To add a server, provide the following information:

Table 5. Server information

Option

Description

Name

The name you want to use to identify the server.

Host Name or IP Address

The IP address or the hostname of the LDAP server. If the IP address is not valid, the appliance waits to timeout, resulting in login delays during LDAP authentication.

* 
NOTE: To connect through SSL, use an IP address or hostname. For example: ldaps://hostname.

Port

The LDAP port number, which is usually 389 (LDAP) or 636 (secure LDAP).

Base DN

The criteria used to search for accounts.

This criteria specifies a location or container in the LDAP or Active Directory structure, and the criteria should include all the users that you want to authenticate. Enter the most specific combination of OUs, DCs, or CNs that match your criteria, ranging from left (most specific) to right (most general). For example, this path leads to the container with users that you need to authenticate:

OU=end_users,DC=company,DC=com.

* 
NOTE: Domain Users is a special group that is not added to the memberof attribute values. For Domain Users members, use this format: (primaryGroupId=513).

Advanced Search

The search filter. For example:

(&(sAMAccountName=KBOX_USERNAME)(memberOf=CN=financial,DC=example,DC=com))

Login

The credentials of the account the appliance uses to log in to the LDAP server to read accounts. For example:

LDAP Login:CN=service_account,CN=Users,

DC=company,DC=com.

If user name and password are not provided, the tree lookup is not performed.

Each LDAP Label can connect to a different LDAP or Active Directory server.

Password

The password of the account the appliance uses to log in to the LDAP server.

Role

(Required) The user’s role:

•
Global Administrator: The user can access the System Administration Console, and each organization’s Administrator Console as an administrator with full read/write permissions. They must first log in to the System Administration Console, and then log in to the applicable organization account using the drop-down list in the top-right corner.
•
Administrator: The user can log in to and access all features of the Administrator Console, User Console, or System Administration Console.
•
Read Only Administrator: The user can log in, but cannot modify any settings in the Administrator Console, User Console, or System Administration Console.
•
User Console Only: The user can log in only to the User Console . This role is only available in the Administrator Console.
•
No Access: The user cannot log in to the Administrator Console, System Administration Console or User Console. No Access is the default role.
* 
NOTE: These roles are predefined and you cannot edit them. However, you can create and edit custom roles as needed.
* 
NOTE: Record the search and filtering criteria you use for filling out this form. You use this same information to import user data, and later to schedule user import on a regular basis.
8.
Click Save.
9.
Test authentication on an external LDAP server as follows:
a.
Select the LDAP Authentication.
b.
Click the Edit button next to the server on which the user account you are testing is located .
c.
In the Advanced Search: box, replace KBOX_USER with the username to test. The syntax is sAMAccountName=username.
d.
Enter the user’s password in the Password for test field.
e.
Click Test.

If the test is successful, the authentication setup is complete for this user, and other users in the same LDAP container.

Importing users from an LDAP server

Importing users from an LDAP server

Import user information manually
Import user information according to a schedule

You can import user information from LDAP servers to create user accounts on the appliance. This provides administrators, such as Service Desk staff, with a richer set of data to use when working with users.

There are two ways to import user information:

•
Manually: See Import user information manually
•
According to a schedule: See Import user information according to a schedule
* 
NOTE: User information is overwritten each time users are imported to the appliance. Password information, however, is not imported. Users must enter their passwords each time they log in to the Administrator Console or User Console.
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択