AACLI plan

[Cantor, Scott]

On 9/26/14, 1:01 PM, "Michael R. Gettes" <gettes at cmu.edu> wrote:

>FWIW, I think you are missing an opportunity here to make the shib IdP
>easier to administer.

I'm not sure why what I just said isn't actually easier than the command
line tool is now, since it also works from a browser. But needing to build
a replacement for the existing tool to maintain functionality is
orthogonal to suggesting we do something entirely new and separate.

But the opportunity to work on real administrative tools for 3.0 was
always a mirage, we can't do a rewrite and take on a giant new project at
the same time.

We do want to do some basic things before shipping like get interfaces in
place to control refresh of metadata and configurations, so there are
predictable ways to get changes applied.

>I appreciate your argument and perspective, but you really should
>consider a tool making it easier to interact with the IdP.

Define "interact". A GUI is a massive project and I don't see it given our
resources, except for eventually getting some web interfaces in place to
monitor certain things and to access certain information as an end user
(like reviewing privacy settings and altering them).

As a deployer, I want files. So it's very hard for me to justify spending
time building tools I would never  consider using and would always advise
against using.

What I really care about is stability, an absolute zero tolerance for
runtime problems. Everything else is secondary to me.

I love the fact that we're now all-in with Spring and the guts are all
hanging out now, which creates a lot more surface area for adding tools
later.

-- Scott