Skip to Content.
Sympa Menu

shibboleth-dev - Re: Soliciting Feedback, Shibboleth 2 Roadmap

Subject: Shibboleth Developers

List archive

Re: Soliciting Feedback, Shibboleth 2 Roadmap


Chronological Thread 
  • From: "Tom Scavo" <>
  • To:
  • Subject: Re: Soliciting Feedback, Shibboleth 2 Roadmap
  • Date: Sun, 12 Mar 2006 12:35:17 -0500
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=MOiKeSrtqpWADHCvIv6xCvBIKREmAeEgf+oTTO8Y6L+3oUY5NQeDDfY9Ydg71HHkdJZ6Utow/3oJ1H07fB9ACepyFjh9NeUdLQgUjtz/Jv6rM5jwaadXDVNjgYTixk7QCvZlHaKIOz1oReGbpgH6x2blibMUOjct87+Rg4w+3is=

On 3/12/06, Velpi
<>
wrote:
>
> * resolver-ARP-metadata management UI (modular)

This is exactly what's needed. Here is what it might do:

- Produce IdP metadata from the underlying config (idp.xml, resolver.xml)
- Publish metadata to a "well-known location" or a metadata repository
- Consume SP metadata and ARPs, provide a UI to administratively merge
the two, and produce new ARPs

So a pair of tools are needed at the IdP, one for metadata production
and another for metadata consumption. Same is true at the SP.

> Question is: do you really want your metadata to be editable easily? I
> guess not, but there are a lot of ways to prevent tampering.

A tool that manages metadata does not need to edit metadata. The UI
above leverages SP metadata to manage policy at the IdP.

Tom



Archive powered by MHonArc 2.6.16.

Top of Page