Yep, that worked for me, thanks. For info, the saml response itself was no longer written out with debug logging on. Kevin
> On 11 Aug 2015, at 18:00, David Hawes <dha...@vt.edu> wrote: > > On Tue, Aug 11, 2015 at 12:06 PM, Milt Epstein <mepst...@illinois.edu> wrote: >> This sounds somewhat like what I ran into last November. I was trying >> to set up CAS 4.0.1, with mod_auth_cas and saml, and I was getting a >> segfault. Turned out mod_auth_cas needed some updating to handle that >> combination. Here's the thread about it (from the mod-auth-cas-dev >> list): >> >> https://lists.wisc.edu/read/messages?id=35937941 >> >> Hopefully it can help you as well. The posts from Steven Maresca are >> probably the most relevant ones. > > As Milt suggests, that thread should be helpful. > > More specifically, try merge request #82 > (https://github.com/Jasig/mod_auth_cas/pull/82) and see if that fixes > it for you. > > 1.0.10 gets the user value from the AttributeStatement. The merge > request above will get it from either the AuthenticationStatement or > the AttributeStatement, ensuring that it is set and can be written in > witeCASCacheEntry(). > > -- > You are currently subscribed to cas-user@lists.jasig.org as: > khsew...@glam.ac.uk > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user -- You are currently subscribed to cas-user@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
