The filter, as it exists today, does not populate that header. It could easily be extended to do that as an option.
Adam Derek Ethier wrote: > Thanks for all the help. We're getting close, but we're not quite > there. I've added the java client files to the lib folder and > configured the web.xml file. request.getRemoteUser is returning the > correct username but the print jobs do not contain the correct user > when the jobs are submitted. > > I'm talking to the vendor to see how they use the REMOTE_USER header. > > Again, thanks for the assistance. If we get it working, I will post a > follow-up with the documentation on how to do it. > > *[email protected] <mailto:[email protected]> on > Thursday, February 18, 2010 at 10:06 AM -0400 wrote:* > _*> The Jasig CAS client for Java can populate that if you add the > filters.*_ > > Specifically, the HttpServletRequestWrapperFilter filter delegates > request.getRemoteUser() to the underlying CAS assertion containing the > user name. As Adam noted, it matters how PrinterOn is attempting to > get at REMOTE_USER; if it's via request.getRemoteUser(), it should > work fine. > > M > > -- > You are currently subscribed to [email protected] > <mailto:[email protected]> as: [email protected] > <mailto:[email protected]> > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > > > -- > 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 -- 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
<<attachment: arybicki.vcf>>
