Voyager SSO via GCF?
Fri, 2008-05-16 18:25 — katya
I've been asked to do some initial research on what will be involved in creating a GCF SSO connector from Luminis IV to Endeavor Information System's Voyager library information system. I see that several other members had varying degrees of success, and wanted to see if people can post their experiences so that I can get an idea of the amount of work that is going to be involved, and what questions I need to ask the Voyager app admin.
The little that I do know about the Voyager system is that it is internally hosted, so I'll have access to the Voyager server to test out the pickup.html method.
Thanks,
Alice Kim
Hack Your Knowledge
Recent blog posts
- Updated to 4.1.22 - Complications
- Time Estimate for Luminis Platform IV Upgrade
- Luminis IV Memory Configuration
- CPIP Novice Looking for HELP!
- Targeted Announcement Permissions and Grants
- Associated Press OSTN Video News Portlet/Channel
- EAS credentials not the same as luminis credentials
- Lumiins start up issues
- Messaging Server Configuration
- User Attributes from Banner
Developer Links
Poll
If there were a Luminis Developers Conference, would you prefer it in -
early spring
14%
late spring
15%
early summer
29%
late summer
8%
early fall
9%
late fall
14%
early winter
8%
late winter
3%
Total votes: 185
Syndicate
CPIP to Voyager
We haven’t gotten anywhere with Voyager yet except to learn some things that don’t work. I got a set of files from Carol Hopkins at Seton Hall (see http://www.lumdev.net/node/1551), but they didn’t work for me. As best I can tell, our implementation of Voyager has IP tracking turned on in the web server so it will not allow transfer of a session started by CPIP over to a client browser. I got info from two other schools on different approaches that seem promising, but I haven’t been able to try either approach yet. Here’s a synopsis.
1) Victoria University at Wellington (New Zealand) – Uses EZProxy to create SSO to Voyager, and uses CPIP to create SSO to EZProxy and transmit the Voyager credentials. (http://www.lumdev.net/node/1000)
2) Monash University (Australia) – Uses Voyager’s external authentication interface, plugging in a module that picks up credentials from their portal (not Luminis) and initiates the session within the Voyager database. I personally think this approach is the most sound.
I'd be glad to share the material I obtained from Seton Hall, VUW and/or Monash. E-mail me at bill_ramsay@berea.edu.
IP tracking the show stopper?
So it sounds like IP tracking being enabled may be the show stopper on this. I'll send you an email to get those files.
Alice Kim