Guidance for app owners: got any? (i.e. "things to think about" before you develop/deploy)
Tom Scavo
trscavo at gmail.com
Mon Sep 23 16:25:04 EDT 2013
Part of the difficulty in responding to your request, Marlena, is that
the purpose and scope of the SP matters. InCommon is focused on
cross-domain SPs (a term I've used before, if you'll recall) but for
the most part, on-campus SPs are out of scope. Of course there is some
overlap, and so you might find some of the InCommon wiki pages useful
as reference material, but you'll pretty much end up having to write
your own set of "recommended practices" depending on any number of
things, including your particular IdP deployment, your attribute
release policy (both local and federation-facing), and so forth.
In any case, I'll wait for Scott to provide his favorite set of
pointers, and then I'll add a few of my own.
Tom
On Mon, Sep 23, 2013 at 4:12 PM, Erdos, Marlena
<marlena_erdos at harvard.edu> wrote:
> Scott,
>
>
>>My first attempt was to start a WG within MACE regarding federated
> application development, and I didn't have the time. My second attempt was
> to draft a number of wiki topics on federated application issues which are
> in the InCommon documentation and were left in varying states, some
> polished up by InCommon.
>>
>
>
>
> Could you provide urls (or search terms) so I could find the InCommon
> articles you drafted? I'd love to see them (and anything else you've
> written addressing "advice to app" owners (whether polished or not).)
>
>
>>Another problem though is lack of consensus on many issues. When you don't
> have broad agreement (or don't know you have it), it's difficult to tell
> people what to do.
>>
>
>
> I'm just not worried about the lack of consensus. Right now, we have
> very little advice that we give to application owners. If I write it, it
> will just be my point of view (modulo reviewers) i.e. a consensus of one
> :-). If instead I have material at hand that espousing a variety of
> views, then I can at least say to users "here are the points of view" and
> "here's how I think you might want to think about your situation"
> (assuming I have details on their situation).
>
> Additionally, even more than "telling people what to do" what I'm
> interested in is providing the app owners a set of *questions* to think
> about along with some example scenarios.
>
> **
>
> If anybody else has some pointers to guidance, I'd much appreciate hearing
> about. (And I look forward to whatever Scott is willing is pass along.)
>
>
> Thx!
> Marlena
>
> --
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
More information about the users
mailing list