Sorry, I realize you tried that already. My comment is in the issue you filed, but for posterity, here it is (and let's keep the conversation in the JIRA issue):
Unfortunately I don't think that this can be resolved (easily) by using a dynamic size at runtime. The response will fail after the service ticket has been presented, so it can't be replayed (the ticket will be invalid). The user would need a 302 redirect back to the CAS server, possibly requiring credential re-entry etc. I guess we could make it configurable, but at 16k with a trivial local workaround, this will be fairly low priority for us. -Phil On Mon, Dec 5, 2011 at 11:57 AM, Phil Ames <[email protected]> wrote: > This limit has been increased in newer versions[1], do you have the option > to compile from source? > > -Phil > > [1] > https://github.com/Jasig/mod_auth_cas/commit/e95e701ea1650e0e18a0e7fcb6d5f470ffb19602 > > On Mon, Dec 5, 2011 at 11:46 AM, Philippe MARASSE < > [email protected]> wrote: > >> Folks, >> >> I've opened a Jira issue for mod_auth_cas 1.0.9.1 : In our organization, >> I use SAML ticket validation an get an "Authorization required" when CAS >> response size is over 4 kb : >> >> https://issues.jasig.org/**browse/MAS-66<https://issues.jasig.org/browse/MAS-66> >> >> It appears that this 4kb limit is hardcoded into mod_auth_cas.h >> (CAS_MAX_RESPONSE_SIZE). As a workaround I set it to 8kb and now it works >> again :-) >> >> I'm wondering if there's not a better solution than pushing the limit... >> Can the curl buffer size being adjusted at runtime ? >> >> Rgds. >> >> -- >> Philippe MARASSE >> >> Service Informatique - Centre Hospitalier Henri Laborit >> BP 587 - 370 avenue Jacques Coeur >> 86021 Poitiers Cedex >> Tel : 05.49.44.57.19 >> >> >> > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
