evolving the JSON schema

Cantor, Scott cantor.2 at osu.edu
Sun Mar 6 14:04:06 EST 2016


On 3/5/16, 10:10 AM, "dev on behalf of Tom Scavo" <dev-bounces at shibboleth.net on behalf of trscavo at gmail.com> wrote:



>EDS-71 [1] suggests that entity attributes might be added to the JSON
>schema. That's great! The InCommon Per-Entity Metadata Pilot is also
>working on a JSON schema. [2] Can we work together on this?

I'm pretty certain I did that a long time ago, which I noted in the issue. I certainly can see the code. If they're not appearing in the feed, might be a bug. I believe it should even support exposing EntityAttributes attached at runtime with a filter.

>In both cases, it would be good if the JSON file aligned with the
>local discovery feed used by the EDS.

Well, I'm aware that we have no standard on this and that SSP uses a different format than I did. I don't have an easy way to evolve mine (C++, remember?) so I don't know that I'm too in favor of me being the one who changes...

Mine's also not signed of course, but any signing would be for server-side code anyway.

-- Scott



More information about the dev mailing list