Preparing for CIFS Authentication
Configuring the NTLM Authentication Server
3-6 CLI Storage-Management Guide
For example, the following command sequence removes a proxy user called
proxyNYC:
bstnA6k(gbl)# no proxy-user proxyNYC
bstnA6k(gbl)# ...
Configuring the NTLM Authentication Server
Before you configure a namespace with Windows NTLM, you must also configure an
NTLM-authentication server for the namespace. The NTLM Authentication Server is
the Windows Domain Controller (DC) that is the host for the Acopia Secure Agent
software. When the ARX gets a request for access from a CIFS client, it passes the
password to the Secure Agent for authentication. As a CIFS proxy, the ARX must also
access back-end CIFS filers; the Secure Agent answers all password challenges as the
same client.
The Secure Agent is required because the ARX acts both as the CIFS server for an
end user and then as a CIFS client on behalf of the same user. The user may request
access to multiple back-end filers, so the ARX must answer multiple NTLM
challenges on behalf of the client. The NTLM protocol prevents the ARX from
holding onto the user’s password, so a secure mechanism is required for retrieving the
user’s password as needed. The Secure Agent, residing on the Windows Domain
Controller, provides this mechanism. The ARX passes the NTLM authentication
challenge and the client’s username to the Secure Agent, which retrieves the client’s
password to answer the NTLM challenge. (The Secure Agent accesses the DC’s SAM
database to get the client’s password hash.) The ARX forwards the challenge response
to the back-end filer, completing the authentication session.
You separately install the Acopia Secure Agent at a DC, then you specify the server’s
IP address (and other parameters) at the ARX’s CLI. Refer to the Secure Agent
Installation Guide for instructions to install the Secure Agent and then configure it at
the ARX.
Comentarios a estos manuales