Relying party parsing. Metadata providers
Cantor, Scott
cantor.2 at osu.edu
Wed Mar 19 15:13:29 EDT 2014
On 3/19/14, 1:10 PM, "Rod Widdowson" <rdw at steadingsoftware.com> wrote:
>I have not reviewed the filters yet, I do not foresee difficulties in
>there
>(but who knows)
The filters are where the security schema comes in, of course.
>I'll leave the warning about of deprecated attributes in place.
Which are deprecated? We may just want to pull them, since this is a major
upgrade.
>The proof will be in the coding, but my current belief is that I will be
>able to explicitly handle the ResourceBackedMetadataProvider by poking
>inside the <Resource> and building one of the other MetadataResolvers.
You mean literally just turning the HTTP case into the other HTTP resolver
on the fly?
>The exception is the Classpath and SVN Resources but for that there is the
>ResourceBackedMetadata provider to fall back onto. It seems unlikely that
>anyone will be using classpath inside any existing IdP deployments and
>improbable that they will be using SVN, is it worth issuing a warning on
>these prior to removing them sometime in the future?
I think some people do use SVN. I probably should be in fact.
-- Scott
More information about the dev
mailing list