Dell PowerConnect 3324 User Manual page 154

• Secure HTTP—Specifies the authentication profiles used for Secure HTTP access.
The possible field values are:
–
–
–
–
–
–
–
–
–
Applying an Authentication List to Console Sessions:
Open the Select Authentication page.
1
Select an Authentication Profile in the Console field.
2
Click Apply Changes. Console sessions are assigned an Authentication List.
3
Applying an Authentication Profile to Telnet Sessions:
Open the Select Authentication page.
1
Select an Authentication Profile in the Telnet field.
2
154 Configuring System Infor m ation
None—Indicates that no authentication profiles is used for Secure HTTP access.
Local—Indicates that Secure HTTP authentication occurs locally.
Radius—Indicates that Secure HTTP authentication occurs at the RADIUS server.
Local, None—Indicates that Secure HTTP authentication first takes place locally. If
the local database is empty, no authentication method is used, and secure HTTP
access is permitted.
Radius, None—Indicates that Secure HTTP authentication first takes place at the
RADIUS server. If the RADIUS server cannot be accessed, no authentication method
is used, and secure HTTP access is permitted.
Local, Radius—Indicates that Secure HTTP authentication first takes place locally.
If the local database is empty, the RADIUS server authenticates the user. If the
RADIUS server cannot authenticate the management method, the Secure HTTP
session is blocked.
Radius, Local—Indicates that Secure HTTP authentication first takes place at the
RADIUS server. If the RADIUS server cannot be accessed, the Secure HTTP session
is authenticated locally. If the Secure HTTP session cannot be authenticated locally,
the Secure HTTP session is blocked.
Local, Radius, None—Indicates that Secure HTTP authentication first takes place
locally. If the local database is empty, the RADIUS server authenticates the
management method. If the RADIUS server cannot access the database, the Secure
HTTP session is permitted.
Radius, Local, None—Indicates that Secure HTTP authentication first takes place at
the RADIUS server. If the RADIUS server cannot be accessed, the Secure HTTP
session is authenticated locally. If the local database is empty, the Secure HTTP
session is permitted.