User Authentication. Novell Security Manager Powered by Astaro

Using Novell Security Manager

Service: The Syslog protocol is set by default. You can also use this dropdown menu to configure the service (port) that should be used on the remote server.

Logs: This selection field allows you to select log files that should be delivered to the remote host.

Novell Security Manager supports User Authentication using the SOCKS v5, SMTP, and HTTP proxy services and can control which users are allowed to use which services. User accounts can be defined on the Security

Manager, through the Definitions/Users menu. Or on an external user database. Supported external databases include RADIUS, SAM (Windows

NT/Windows 2000/XP-Server), Microsoft Active Directory, the domain joining method of NTLM and OpenLDAP. If an external user database is already present on the network, you can use it instead of having to reenter user accounts on Novell Security Manager itself.

Important Note:

Please note, that several authentication methods cannot be supported at the same time.

In MS Windows based networks the Domain Controller (DC) manages access to a set of network resources (e.g., applications, printers, etc.) for a group of clients. The user needs only to log in to the domain to gain access to the resources. A Domain Controller is a server that is running a version of the MS Windows 2000 Server or 2003 Server operating system and has Active Directory (AD) installed, which is Microsoft’s trademarked directory service.

A directory service provides a centralized location to store information in a distributed environment about network devices, services, and the people who use them. For MS Windows users it provides account information, privileges, profiles, and policy. When an authentication method is used together with Active Directory and with the corresponding settings, the authentication, e. g. before accessing an own Service is no longer made by

Novell Security Manager but by the Active-Directory-Server.

User Authentication requires users to identify themselves before using network services. In comparison with an IP-based access control the userbased access control allows for user-based Accounting in the HTTP proxy access protocol.

52