Shibboleth Developers

["Scott Cantor" <>]

> In order to provide our end-users with a central directory of all
> available Service Providers and for other things of our federation, we
> are thinking of creating an XML file (using the data of our Resource
> Registry) that describes our federation in a complementary way than the
> federation metadata and individual XML files.

I think everything you're asking for is already in those files.

> This e.g. means that:
> - all supported attributes within the federation are listed

You can publish a global AAP file with this information.

> - additional contact information for each SP/IdP is listed

In the metadata.

> - the required/desired attributes for each Service Provider is listed

In the metadata.

> - the intended audience of an Service Provider is listed

No such thing anymore, it is merely the providerId.

> - and so on

You'd have to come up with something new to justify a new file, I think.

-- Scott