Multiple Vhosts - one end point

Peter Schober peter.schober at univie.ac.at
Sun Oct 9 17:25:40 BST 2011


* Tom Scavo <trscavo at gmail.com> [2011-10-09 17:10]:
> On Fri, Oct 7, 2011 at 5:12 AM, Peter Schober
> <peter.schober at univie.ac.at> wrote:
> > Assuming you don't want to compile and run your own code you'd then
> > either have to add a new ACS URL for every new vhost to an existing
> > <EntityDescriptor> describing your SP (making all vhosts part of one
> > logical SP), or have seperate <EntityDescriptor>s for every new vhosts
> > (making every vhost a new logical SP).
> > If you also want the IdP to differentiate these reources at the IdP
> > (by sending them different sets of attributes) you'll be stuck with
> > the latter method.
> 
> In practice, yes. In principle, multiple AttributeConsumingService
> elements in metadata would serve the same purpose. I wonder if we'll
> ever get there...

Are you're suggesting to enhance the IdP to allow policy
(e.g. attribute filtering) decisions based on ACS URLs?
-peter


More information about the users mailing list