Access Manager allows you to use Kerberos as a method for authenticate users accessing protected resources (see the Novell Access Manager documentation for details). This is a great feature but can also significantly increase the complexity of your Access Manager deployment.

Background: Access Manager SSO is based on Kerberos authentication. Each user that logs in to the corporate domain is issued a Kerberos ticket by a domain controller. This ticket is requested by the Access Manager server at the time a SSO site is accessed. The browser presents the SPNEGO token in the HTTP header of the request for the SSO enabled resource. This SPNEGO token is a wrapper of the Microsoft Windows Kerberos token. Microsoft Windows includes the user’s PAC information in the Kerberos token. The more security groups that the user belongs to, the more PAC information is inserted in the Kerberos token, and the larger the SPNEGO token becomes. Apache Tomcat 5 limits the size of any acceptable HTTP header to be 8K by default. In Microsoft Windows domains having many groups, and with user membership in many groups, the size of the user’s SPNEGO token may exceed the 8K limit.

The Symptom: When a user requests access to a protected resource they are re-directed to the Identity Server for authentication. The Identity server then requests the browser to re-request the page and this time include the SPNEGO token in the HTTP header of the request. If the browser sends a request that has a header size larger than the default 8k limit, Apache Tomcat abruptly closes the TCP connection. To the user, this will simply appear as “Page cannot be displayed” in Internet Explorer and Firefox. Since Tomcat is brokering the communications between the browser and Access Manager, there will be no errors or any indications whatsoever of a problem in the Access Manager logs. Also, by default, Tomcat does not log why the connection was closed.

Verify the Problem: There are two thing you can do to verify that this is the actual problem you are having. The first is to do a packet trace between the browser and Identity Server. You should see a GET packet that includes the SPNEGO token listed under AUTHORIZATION in the HTTP header. If the header of that GET packet is over 8kb, you will see this issue.

The second thing you can do is get the TOKENSZ utility from Microsoft. Run the following command on the workstation that is having difficulty authenticating to the Identity Server…

tokensz /compute_tokensize

In the output, you will be looking for <strong>MaxToken</strong>. This is the size of this particular user’s Kerberos Token. Keep in mind that even if the size of this token isn’t over 8192 bytes, it’s the COMBINATION of this token and the rest of the HTTP header (which will vary in your environment) that will be limited to 8192 bytes.

The Solution: You can adjust the HTTP header size that Apache Tomcat will accept (and thus pass along over to Access Manager for authentication). To do this you will need to edit the following file (valid for Access Manager 3.1.1 and most likely any 3.x version)…


Within this file, look for a line starting with the following…

<Connector NIDP_Name="connector"

At the end of this line, add the following parameter…


In our environment we chose a 32k max header size in the hopes that we will never have to deal with this issue again but you can also do something like 16384 for a 16k maximum header size if you choose. Tomcat will allocate 2 buffers of 32kb per connection (one for input and one for output). Yes, your server will use up a bit more memory in this configuration, but considering the connection to the IDP are usually short lived, it shouldn’t be much of an issue.

Once you’ve made this change, save the file and bounce Tomcat or bounce the server to change the running configuration.

1 vote, average: 5.00 out of 51 vote, average: 5.00 out of 51 vote, average: 5.00 out of 51 vote, average: 5.00 out of 51 vote, average: 5.00 out of 5 (1 votes, average: 5.00 out of 5)
You need to be a registered member to rate this post.
Categories: Uncategorized

Disclaimer: As with everything else at NetIQ Cool Solutions, this content is definitely not supported by NetIQ, so Customer Support will not be able to help you if it has any adverse effect on your environment.  It just worked for at least one person, and perhaps it will be useful for you too.  Be sure to test in a non-production environment.

Leave a Reply


  • TellierS says:

    Hi, I have a AD kerberos SSO and I want to verify the access to a resource via a group in the LDAP (eDir) provider (already used to retreive eDir password).
    Is it possible?
    If I use a login form with eDir as provider, it works fine, but not when I use kerberos first.
    Have you an idea to resolve my issue?

  • cmendes says:

    For NAM 4.X, the correct line to be changed is <Connector port="8443"

    The line should look something like

  • MatthewEhle says:

    This solution just saved me a lot of troubleshooting headache. Well done!

  • Alexander McHugh Alexander McHugh says:

    When the IDP is behind an Access Gateway, one must adjust the maximum header size in Apache on the AG also.

    This is done by inserting the line:

    LimitRequestFieldSize 32768

    before the existing line

    Include /etc/opt/novell/apache2/conf/vhosts.d/*.conf

    in the apache httpd.conf file.

    On windows, this is located at “C:\Program Files\Novell\apache\conf\httpd.conf”

    Be sure to use the same max header size in Apache (AG) and Tomcat (IDP) and don’t pick a larger value than absoluetly necessary to ensure that overall performance is not adversely impacted by this adjustment.

By: bdgreen
Jun 11, 2010
7:03 pm
Active Directory Authentication Automation Cloud Computing Cloud Security Configuration Customizing Data Breach DirXML Drivers End User Management Identity Manager Importing-Exporting / ICE/ LDIF Intelligent Workload Management Knowledge Depot LDAP Monitoring Open Enterprise Server Passwords Reporting Secure Access Sentinel Supported Troubleshooting Workflow