Single Sign On

Project Background Our company has two distinct web-based tools for customers; one allows customers to view account information (quotes, orders, invoices, etc), and the other is for collaboration and project management. The systems are both proprietary and are made by different vendors. We would like to customers to be able to access both systems with only entering credentials once. We would also like customers to be able to click on a part number in the account management site, and be taken to the associated project in the project management site, either in a new browser window or new tab. Site A - Account Management Web Site We will refer to the Account Management platform as Site A. Site A taps into our ERP system and allows customers to view quote, order, invoice, inventory and shipping information. The site runs on IIS, is written in asp.Net and has a Silverlight front end. The vendor for Site A is relatively helpful and is willing to work with us in developing a solution. Site B - Project Management Web Site We will refer to the Project Management platform as Site B. Site B taps into our workflow software and allows customers to collaborate with artists and sales people, upload or download documents, manipulate documents, and approve or reject changes. The site runs on Tomcat and is written in JSP. The vendor for Site B will only offer help when extremely large checks are written. Both systems are hosted in-house, are on the same subnet and use a Microsoft SQL back end. Platform Summary Site A Server Windows Server 2000 Web Server IIS 6 Language Asp.Net Database MS SQL 2000 Vendor Cooperative SSL No Domain member Yes Site B Server Windows Server 2003 R2 Web Server Tomcat Language JSP Database MS SQL 2005 Vendor Non-cooperative SSL No Domain member No Project Scope From within Site A, authenticated users will be able to click on a View button of an existing part number that will launch a new browser window or tab, automatically log them into Site B and open the project corresponding to that part number. The vendor for Site A will be responsible for adding the link in Site A and exporting data to Site B in the format of the developer’s choosing. The developer will essentially be responsible for taking the login credentials and part number from Site A, in the format or manner of his or her choosing, logging the user into Site B, dropping the part number into Site B’s search and displaying the project for the particular part number. Assumptions • Data will travel one way, from Site A to Site B. • No data will need to be modified or stored in either system - this is essentially a login followed by a query (for the Part number). • Usernames and passwords between both systems will be the same. • Part numbers and Project numbers between both systems will be the same. • Any modifications that need to be made inside Site A will be performed by the vendor. • The data coming into Site B from Site A will be in whatever form the developer (you) needs it (plain text, Web Services, XML?). • Developer will have access to both of our production systems. • If needed, the developer will have an opportunity to talk to developers with vendor of Site A. Project Approach Based on the information we currently have about both systems, we think our approach to the solution makes sense, but we are more than willing to listen to any other reasonable approach to an SSO solution. The chosen candidate will be paid to visit the project team at our site, review both systems and related documentation, and formalize the work plan. The actual coding work can be performed remotely. The chosen candidate is expected to deliver a functional SSO system, detailed documentation of the project and well-commented code.