SP computation of the ACS URL to include in <AuthnRequest>

[Cantor, Scott]

> Will you entertain an RFE? I understand that it will not be a
> high priority.
> 
> Essentially I want (I think) a configuration option or some mechanism to
> signal to the SP which ACS to use. Something like "I know what
> I am doing, so please just use this ACS URL when constructing
> the <AuthnRequest>".

I think there are a number of related options that might make sense, such as just not overriding the template, handling shared domains differently, etc.

Also, I thought you could actually control the ACS explicitly by using indexes (which is hard to do, but I thought it worked). If you set the acsByIndex flag in the config, and then pass in acsIndex on the redirect, I think that works. The problem is getting the indexes to match the metadata. I dropped that whole avenue because the indexes the SP processes are its own whereas the IdP has to match it to what's in the metadata, and they usually don't match. But they can, it's just tricky.

-- Scott