We have just had our Luminis IV test environment installed and with SunGard's assistance, integrated with Banner SSB and INB. Our rollout in production will be in September.
SunGard has given us a proposal to write SSO connectors to some of our other systems, including PeopleSoft, Oracle Calendar, Blackboard, Voyager and FAMIS. We are debating whether we should hire SunGard to do the work, or take the classes and learn to do it ourselves. From the amount of information posted here, it appears that many institutions are successfully developing their own connectors. With the right resources, does it seem reasonable we could accomplish this on our own? Is there a list someplace of connectors that have been developed?
As Luminis newcomers, any other thought or advice would be appreciated.
Paul T. Webb
University of Vermont
Peoplesoft SSO
Our HR system here is PeopleSoft, and we have written an employee pay information channel, complete with single sign-on into PeopleSoft self service. Let me know if you want to see the code.
Todd
Found GCF training engagement useful
Paul - we purchased the on-site training engagement for GCF (Generic Connector Framework) from SunGard and found it very useful. By the end of the week we had sso connectors in place for Blackboard 7.2, MS Exchange 2007 webmail and our Library EZProxy interface to journal subscriptions. Since then we have set up sso for our Barracuda SPAM filter and a couple of our own ASP.NET applications. With Lumins IV, the GCF is part of the package and there is good documentation for it and for the CPIP subsystem itself. The build or buy decision will be based on your own staffing and expertise development strategy, but I'd save the outsourcing for something more complex.
Interested in sso to Voyager
Paul - I noticed Voyager in your sso wish list. We have not been successful using GCF to access Voyager because our installation is apparently doing server side IP tracking. I'd be interested in partnering with your team in working out the interface. I'm aware of three approaches folks have found successful. Seton Hall U. used basic GCF, so I assume their Voyager installation is not doing the IP tracking. Monash U. (Australia) is using Voyager's external authentication API to create a trusted interface from Luminis, and this is the approach I find most appealing. U. of Victoria at Wellington (New Zealand) is using EZProxy to establish sso to Voyager and then doing sso to EZProxy from Luminis - another intriguing approach. Please keep me posted (bill_ramsay@berea.edu) on how your team is doing with Voyager. Thanks.