Shibboleth Developers

[Velpi <>]

> > > Unassigned Features
> > >
> > >     * ARP and Attribute resolver management UI
> >
> > How is this different than MAMS ShARPE?
>
> ShARPE doesn't do resolver management and as of yet does not have a 
> release timeline.

While we're at it:
* metadata management UI
...
this all would eventually most likely become sth like:
* resolver-ARP-metadata management UI (modular)

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.


Metadata management might even include a request form to join a certain 
"federation" (aka "Resource Registry"). That might go as far as warning 
when certificates are near to passing their validity period...

Maybe it is interesting to think of putting a reference inside the 
metadata itself (if allowed by the spec) that can tell where a (program) 
should go fetch an update. The number of metadata files on a system will 
increase as federations start to coöperate...


Whatever happens, "modular" and "code/library re-use" should be on top 
of the list for every component surrounding Shibboleth -I think-, so 
it's easy to fit all the pieces together.


--Velpi