Shibboleth Developers

["Scott Cantor" <>]

> There are so many possible requirements that I have always tried to
> advertise the RM (Filter) as example code that a programmer can customize
to
> the requirements of the application. However, I am casting around for a
> "philosophy" or "best practice" to document and I don't think that
> constantly deferring decisions to the SP is anything that one would have
> designed for Java if the syntax had not already been around for the other
> languages and web servers.

I was just saying I think the code shouldn't need to presuppose anything if
it accesses the information using an interface that you can plug anything
behind.

> If I start without presupposition and as how I think a general purpose
> plug-in RM would be designed when there is a Web Application (WAR) with
> different resources having substantial differences in their authentication
> requirements, I suspect the answer would be to deploy more than one Filter
> mapped to different URLs, or at least more than one instance of the Shib
> Filter with different URL mappings and different initialization
parameters.

I didn't know that was possible. That seems like an option.

> So consider the title of this message amended from "Multi-Application
> Contexts" to "Single <Application> Filters", allowing for more than one
> Filter per Context when it makes sense.

That doesn't seem unreasonable to me, but I'd defer to actual Java
developers for the final judgement.

-- Scott