Task #3394: Deploy Shibboleth provider for KNB LDAP accounts
Establish InCommon partner or CILogon partner status.
To have the KNB provider be recognized, we need to have the InCommon federation or CILogon to recognize the KNB provider.
#2 Updated by Ben Leinfelder almost 9 years ago
- Status changed from New to In Progress
I spoke with Jim Basney at CILogon about the options for becoming an InCommon member. In order of "best fit", they are:
Become an InCommon member as an independent Research Center¶
Either UCSB or UIC could "sponsor" us -- really just an email to InCommon¶
L4 (fewer than 2000 full-time employees) is $1180 per year, after a $700 initial fee¶
This gives us complete control over our InCommon membership¶
Optionally add another IdP (unaffiliated accounts), but at the cost of $1000 per year.¶
Have UCSB add us as an IdP on their account¶
Would be $1000 per year for that.¶
We would not have direct control of our IdP metadata/InCommon registration.¶
#4 Updated by Ben Leinfelder almost 9 years ago
First draft of application is here for review and discussion. There are some TBD items noted in the POP document.