Amer Networks E5Web GUI - Manual (Page 520)

Chapter 8: User Authentication
This chapter describes how cOS Core implements user authentication.
• Overview, page 520
• Authentication Setup, page 522
• ARP Authentication, page 542
• Customizing Authentication HTML Pages, page 544
• Policies Requiring Authentication, page 548
• User Identity Awareness, page 550
• Two Factor Authentication, page 556
• Radius Relay, page 558
8.1. Overview
In situations where individual users connect to protected resources through the Clavister
Security Gateway, the administrator will often require that each user goes through a process of
authentication before access is allowed.
This chapter deals with setting up authentication for cOS Core but first the general issues
involved in authentication will be examined.
Proving Identity
The aim of authentication is to have the user prove their identity so that the network
administrator can allow or deny access to resources based on that identity. Possible types of
proof could be:
A. Something the user is. Unique attributes that are different for every person, such as a
fingerprint.
B. Something the user has, such a passcard, a X.509 Digital Certificate or Public and Private Keys.
C. Something the user knows such as a password.
520