alternative-idp - other strategies that still involve the open source IdP stacks
Subject: Alternative IdP Working Group
List archive
- From: Scott Koranda <>
- To:
- Subject: other strategies that still involve the open source IdP stacks
- Date: Wed, 20 Aug 2014 11:40:14 -0500
Hello,
In the grid that we have constructed so far both Shibboleth and
SimpleSAMLPhP (local) are single rows, assuming that the operator is
going to download, configure, and deploy in the usual way that the
larger organizations have done in the past.
For each of those two software stacks I can envision two more strategies:
- taking each software stack and re-packaging it to include InCommon
specific boilerplate configuration as well as documentation
- pairing a small organization with an "InCommon approved"
facillitator/consultant to help guide the organization from initial
contact up through on-going operations. The facilitator/consultant
relationship would be "light weight" in that a small organization
would not have to go through the usual proposal/SOW/contract
negotiation. Perhaps InCommon has an arrangement to offer X hours of
"free" consulting to small organizations, or maybe the consultant has
a simple "pay by the hour with a credit card" offering.
The two strategies above could also be extended for ADFS to some extent.
Thoughts?
Are these types of strategies within scope for this group?
Thanks,
Scott
- other strategies that still involve the open source IdP stacks, Scott Koranda, 08/20/2014
- Re: other strategies that still involve the open source IdP stacks, Janemarie Duh, 08/25/2014
- RE: other strategies that still involve the open source IdP stacks, Chalmers, Alex, 08/25/2014
- Re: other strategies that still involve the open source IdP stacks, Scott Koranda, 08/26/2014
- <Possible follow-up(s)>
- Re: other strategies that still involve the open source IdP stacks, Scott Koranda, 08/26/2014
- Re: other strategies that still involve the open source IdP stacks, Janemarie Duh, 08/25/2014
Archive powered by MHonArc 2.6.16.