Set an attribute as REMOTE_USER but don't pass the attribute in the forwarded request

[Bradley Wagner]

Is it possible to map an attribute, set it as the REMOTE_USER but then
*not* pass the attribute along in the forwarded request.

We're running into an issue where an attribute that we're passing is
clashing with a request attribute name that we're using elsewhere in
our app.

It would be easy for us to pull it out of REMOTE_USER and at that
point we wouldn't need the attribute's original name in the request at
all.

We're forwarding to our Tomcat app via AJP. Could I just remove the
"AJP_" attribute prefix and prevent the attribute from being passed to
Tomcat?

Apologies if this has been covered. I did some quick searching and
couldn't find an answer.