Configuring The Access Gateway For Kerberos Authentication - Novell ACCESS MANAGER 3.1 SP2 - IDENTITY SERVER GUIDE 2010 Manual

Identity server guide
Hide thumbs Also See for ACCESS MANAGER 3.1 SP2 - IDENTITY SERVER GUIDE 2010:
Table of Contents

Advertisement

6 (Conditional) If you have users who are outside the firewall, they cannot use Kerberos.
SPNEGO defaults first to NTLM, then to HTTPS basic authentication. Access Manager does
not support NTLM, so the NTLM prompt for username and password fails. The user is then
prompted for a username and password for HTTPS basic authentication, which succeeds if the
credentials are valid.
To avoid these prompts, you can have your users enable the Automatic logon with current user
name and password option in Internet Explorer 7.x. To access this option, click Tools > Internet
Options > Security > Custom Level, then scroll down to User Authentication.
5.5 Configuring the Access Gateway for
Kerberos Authentication
If you have set up a Web server that you want to require Kerberos authentication for access, you can
set up a protected resource for this Web server as you would for any other Web server, and select the
name of your Kerberos contract for the authentication procedure. For instructions, see
Protected
Resources" in the
When using Kerberos for authentication, the LDAP credentials are not available. If you need LDAP
credentials to provide single sign-on to some resources, see
Retrieval," on page
148.
Novell Access Manager 3.1 SP2 Access Gateway
Guide.
Section 4.5, "Configuring Password
Configuring for Kerberos Authentication 171
"Configuring

Advertisement

Table of Contents
loading

Table of Contents