SP configuration for different WAYF services

[Peter Schober]

* Samsamoddin Rajaei <Samsamoddin.Rajaei at bsb-muenchen.de> [2023-02-10 10:41]:
> Hello everybody,

Please don't reply to old, unrelated posts (here "SP doesn't forward
variables" from Oct 2022 CE) when you want to ask a new, different
question. (Changing the subject line is not sufficient.)

> What I currently have, is the following configuration, which
> forwards all requests from APP1 and APP2 to the same WAYF site:
>  
> 	<Host name="www.mydomain.com" applicationId="myHost" authType="shibboleth" requireSession="true"/>
> 	.
> 	.
> 	.
> 	<ApplicationOverride id="myHost" entityID="https://www.mydomain.com/shibboleth">
> 			<Sessions  lifetime="28800" timeout="3600" checkAddress="false" 
> 			           handlerSSL="true" cookieProps="https" relayState="ss:mem"
> 					   idpHistoryDays="7" redirectLimit="exact">
> 					<SSO discoveryProtocol="SAMLDS" relayState="cookie"
> 							discoveryURL="WAYF-1">
> 							SAML2
> 					</SSO>
> 			</Sessions>
> 			...
> 	</ApplicationOverride>

What web server is this for (IIS? Apache httpd? ...)
Why do you need an ApplicationOverride for the above?

Anyway, you can set "discoveryURL" for specific paths (relative
request URI), e.g. ShibRequestSetting discoveryURL SOME_URL
without any ApplicationOverrides. Read The Fine Documentation here:
https://shibboleth.atlassian.net/wiki/spaces/SP3/pages/2065334723/ContentSettings

-peter