On 30 June 2016 at 12:40, mostolog <[email protected]> wrote: > Hi > > > Finally, I managed to solve it. > > Seems that cas-attribute headers are only sent if CASAuthNHeader directive > is enabled.
That's correct. Also note that you may want to set your CASAttributePrefix to something that does not contain underscores, as Apache 2.4 will silently drop those headers. > According to documentation: > > Directive: CASAuthNHeader > Default: None > Description: If enabled, this will store the user returned by CAS in an HTTP > header accessible to your web applications. > > > IMHO that's not exactly what's happening, and either of two should be done: > > Fix an error(if any) to return headers always (but when > CASScrubRequestHeaders enabled?) > Update documentation to reflect this directive also has an effect on > cas-attribute headers > > > Should I fill the issue? Which one? The headers are currently coupled to CASAuthNHeader mostly because of how authorization has evolved over the years, but I could be convinced that they should have their own directive or even be on all the time. In the short term documenting this better would help. Feel free to open an issue discussing all of this, and we can decide what to do there. -- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/a/apereo.org/group/cas-user/. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/CAAgu-wA90THLJH-oc7RkRTVvH%2BxCdhTzBxNxSMGz%3DH%2BXjaZ-%2Bg%40mail.gmail.com. For more options, visit https://groups.google.com/a/apereo.org/d/optout.
