options for using wildcard or shortcuts for URL's in shibboleth2.xml and sp metadata

[Ewing, Bill]

I am setting up a linux sp that will have some sites needing single factor and other requiring 2fa step up. The stumbling block im running into is this application will have way too many url combinations to list and I am trying to find a way to either wildcard a path with */test etc or some other form of shortcut.

For example the url I am needing to setup the override for is https://testsp.test.org/123/testenv/employee/ab/cd/ . the static bits in all the variations are hostname and "/testenv/employee". The path /123/ has one other variation of /456/ but the later paths can be a long list of options and various path depth of 2-4 layers deep.

So in short is there a way to wildcard the handlerurl and various metadata urls needed for the applicationoverride such that we can avoid having to be explicit in the path for however many  variations there are for example: https://testsp.test.org/*/testenv/employee/*/Shibboleth.sso

My example in context of the applicationoverride:
<!-- Step-up 2-factor  -->
<ApplicationOverride id="stepup2f">
   <Sessions lifetime="28800" timeout="3600" handlerURL="/*/testenv/EMPLOYEE/*/Shibboleth.sso" handlerSSL="true" cookieProps="https>
     <SessionInitiator type="Chaining" Location="/stepup2fa" isDefault="false" id="utds2fa" relayState="cookie" authnContextClassRef="duo">
       <SessionInitiator type="SAML2" template="bindingTemplate.html"/>
     </SessionInitiator>
   </Sessions>
</ApplicationOverride>

Any direction or examples or a flat out no you cant do that would be appreciated.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20171115/e42e90f0/attachment-0001.html>