Kerberos Authentication
Use this feature to congure the device (multi-function peripheral, or digital sender) to authenticate users to a
Kerberos Realm. When Kerberos authentication is selected as the Log In Method for one or more Device
Functions on the Authentication Manager feature, the user at the device must enter valid credentials to gain
access to those functions (username, password, and realm).
Authentication consists of two interdependent parts:
●
The device veries the user's credentials with the Key Distribution Center (KDC).
●
After the device user has supplied valid credentials and has been authenticated, the device searches for the
user's email address and name.
If either step fails, the user is denied access to the functions that have been congured to require Kerberos
authentication.
Accessing the Kerberos Authentication Server
The Kerberos realm (domain) is the fully qualied domain name of the Kerberos realm (domain).
Use the Advanced button to the right of the Kerberos realm (domain) eld to access the Alternate Domain
Conguration. Alternate domains are mapped to the default realm.
The Kerberos server hostname can be the same as the Kerberos realm (domain) if a DNS (Domain Name Service)
service is available and correctly congured. The device will use DNS to look up the rst available KDC (Kerberos
Domain Controller) on the network. If DNS is not available, the IP address of the Kerberos Server may be used.
The Kerberos server port is the default IP port used by the Kerberos authentication method. The default is port
88, but this can be dierent in dierent network environments. Please contact your IT administrator to
determine the appropriate port if the default port does not work.
Accessing the LDAP Server
The LDAP server bind method determines how the device will access the LDAP server.
The Credentials conguration section is used to determine which credentials will be used to bind (authenticate)
to the LDAP server.
●
When Use device user credentials is selected, the device users credentials (entered at the control panel of
the device) will be used to access the LDAP server. This method has the advantage of not having to store a
username and password, which may expire, in the device.
●
When Use public credentials is selected and user credentials are not available, the Username and Password
entered will be used to access the LDAP server. This method should be used if for some reason device
users do not have read access to the LDAP data.
The Bind prex setting is the LDAP attribute used to construct the user's Distinguished Name (DN) for
authentication. This prex is combined with the username typed at the control panel to form the Relative
Distinguished Name (RDN). Commonly used prexes are "CN" (for common name) or "UID" (for user identity).
The Bind and search root value is used to validate the user's credentials with the LDAP server. This value is
combined with the RDN to construct the full Distinguished Name (DN) of the user.
The string consists of "attribute=value" pairs, separated by commas. For example:
ou=engineering, o=HP, c=US
428 Chapter 6 Device Conguration Options ENWW
Komentarze do niniejszej Instrukcji