Mods to MetadataGenerator

[Misagh Moayyed]

I am contributing to an open source project, pac4j, which intends to 
auto-generate metadata and it has an exact idea of what bindings it wants to 
support out of the full SAML spec. It obviously provides no corresponding 
endpoints for the bindings that are declared in the metadata, but just for 
sanity, I think it helps if the project is able to generate an exact 
metadata spec for the exact endpoints it does support, (and the ports that 
could be used for dev in cases where 443 is unavailable) rather than 
requiring a user of that project/framework to comb through the file by hand 
and clean out things that are unsupported.

I am sure we could get by as things are now, but this seems like a modest 
enhancement at no significant cost. The class already does an excellent job, 
and this sort of thing will allow alternative idps to leverage existing 
functionality. It's basically a fancy wrapper around an XML writer. I don't 
know if it can get any fancier or more robust than that :)

Misagh

> -----Original Message-----
> From: dev [mailto:dev-bounces at shibboleth.net] On Behalf Of Cantor, Scott
> Sent: Tuesday, December 22, 2015 9:38 AM
> To: Shib Dev <dev at shibboleth.net>
> Subject: Re: Mods to MetadataGenerator
>
> On 12/22/15, 11:07 AM, "dev on behalf of Misagh Moayyed" <dev-
> bounces at shibboleth.net on behalf of mmoayyed at unicon.net> wrote:
>
>
>
> >Reviewing the MetadataGenerator, I want to suggest a few changes so it’s
> easier to extend the class for custom use cases:
>
> I'm not sure we really would want it being used for much of anything else.
> That isn't any kind of robust tool for generating metadata and I don't 
> think it
> was intended as such.
>
> Not saying a few tweaks would be hard or anything, just wondering about
> the general idea.
>
> -- Scott
>
> --
> To unsubscribe from this list send an email to dev-
> unsubscribe at shibboleth.net