• Type: Bug
• Resolution: Not A Defect
• Priority: Major
• Component/s: negotiate-sso-plugin
• Labels:

  • jetty
• Environment:

  Jenkins 2.7.4 on Windows Server 2012.

[JENKINS-38701] HTTP 413 when using kerberos to authenticate

Andrew Ducker created issue - 2016-10-04 14:51

Andrew Ducker made changes - 2016-10-04 14:53

Description

Original: Running Jenkins as a service using the standard method (i.e. running it directly, not in a container) ActiveDirectory plugin was/is working fine. I added the "Negotiate SSO Plugin" and it immediately started returning 413 errors, which indicates that the header is too large (a known problem with Kerberos).

New: Running Jenkins as a service using the standard method (i.e. running it directly, not in a container) ActiveDirectory plugin was/is working fine. I added the "Negotiate SSO Plugin" and it immediately started returning 413 errors to all requests, which indicates that the header is too large (a known problem with Kerberos). It does this to all calls from IE and Chrome. Checking the documentation for Waffle, there are various methods of increasing the header size - but I can't see how to do so for the version of Jetty that Jenkins is embedded in: https://community.jalios.com/jcms/jx_73408/en/windows-authentication-waffle-plugin-1-4?cid=jc2_245325

Christoffer Haglund made changes - 2016-11-02 13:55

Comment

[ Is it possible to configure a connector with higher allowed header request size using the method described on http://stackoverflow.com/questions/38929964/jetty-winstone-connector-configuration-in-jenkins ? ]

Bryson Gibbons made changes - 2022-11-03 19:24

Released As		New: Readme update
Resolution		New: Not A Defect [ 7 ]
Status	Original: Open [ 1 ]	New: Fixed but Unreleased [ 10203 ]