Tested Platforms
- RHE 4 has been tested as an SP on Apache 2.0 and 1.3
- Solaris 10 has been tested as an SP on Apache 1.3
- Windows Server 2003 has been tested as an SP using IIS 6.0
Platforms yet to test
- Solaris 9 has not yet been tested as an SP on Apache 1.3
- Mac OS X has not yet been tested on Apache 1.3
- Windows has not yet been tested on Apache 2.x
Other Prototype Tasks:
Move the existing IdP and SPs to using MIT CA certs
What platform does NIST want to use to host the WebAuth server when we move to pilot?
- Move the WebAuth server to same platform
What platform does NIST want to use to host the Shibboleth IdP when we move to pilot?
- Move the IdP to the same platform
Install and test ArpEdit
UI designer:
- for Webauth login page.
- for confirmation page.
- Do we want to make this have a short redirect, or do we keep it the way it is?
If we go down the path of having a second IdP + login server + ldap server + accounts registration system for external users that don't need an MIT ID we have a whole other set of planning issues and testing that need to be addressed.
Instantiate second IdP and WAYF
Test an SP that also has meta-data for ProtectNetwork.com?
- WAYF at MIT to support other IdPs
- 2nd IdP at MIT?
- ProtectNetwork
- InCommon (once agreements are signed)
Are there new attributes that we want for some internal MIT usage? For example, should we be able to provide the user's MIT ID number as an attribute? We would have to limit the MIT ID to certain SPs or limit its assertion to affiliates and employees to other MIT SPs.
- MIT ID number (limited circumstances)
- LOA for a particular user (eg has an MIT ID Card been issued to the user)
- Type of MIT ID Card issued?