SP attributePrefix question

[Tom Poage]

Morning,

I'm attempting to set up two paths in the same Apache httpd (virtual) host that prepend a different attribute prefix for each; one employs AJP to Tomcat. Same entityID. E.g.

<Location /path1>
  AuthType shibboleth
  ShibRequestSetting requireSession 1
  require valid-user
</Location>

<Location /path2>
   AuthType shibboleth
   ShibRequestSetting requireSession 1
   #ShibRequestSetting applicationId ajp
  Require valid-user
  ProxyPass ajp://localhost:8009/myapp/
</Location>
 
Setting attributePrefix="AJP_" on <ApplicationDefaults> works as expected, in that the AJP connector accepts those variables with the prefix and strips off the prefix by the time it gets to the application environment. e.g. "AJP_sn" gets mapped to "sn". In the httpd environment the the variable names remain "unstripped".

So I'm hoping to find a way to create consistent variables names across applications without any unusual Apache httpd contortions cf. mod_env and friends, i.e. make it easy for application developers and sysadmins to maintain.

Reviewing the docs, it looks as if attributePrefix="AJP_" on an <ApplicationOverride> (leaving it out of <ApplicationDefaults>) might work.

  <ApplicationOverride id="ajp" attributePrefix="AJP_"/>

then enable the ShibRequestSetting (above). This loops when I visit the AJP-enabled path.

I suspect I might need to flesh out ApplicationOverride with a Sessions element and a different handler URL, create a different virtual host (not what I was trying to do),  or create a different entityID for the second app.

Which way do I turn?

Thanks.
Tom.