[Eagle-i-admins] Authentication via Shibboleth

[Bourges, Daniela]

Hi Joshua,
To the best of my knowledge nobody has implemented eagle-i with Shibboleth. NYU implemented eagle-i with a CAS-based authentication method, which involved a few code changes - some of which haven’t been incorporated into the main codebase yet. Unfortunately we don’t have a plug-in mechanism for authentication methods, but I'd imagine NYUs approach could be generalizable (with a bit more coding). Let us know if this would be of interest to you - we can dig out some more information, and put you in contact with the developer that worked on NYU’s changes.

The eaglei.identity.url property was used by our central search application in the early prototype phase, before it was open to the public. The search app is now fully open hence the property is deprecated. 

Cheers
Daniela


Dr. Daniela Bourges-Waldegg
Lead Architect, Harvard Catalyst
Harvard Medical School

Daniela_Bourges at hms.harvard.edu
skype: dbourgesw
phone: 617-384-8898 (NEW)



On Jun 30, 2014, at 12:26, Lease, Joshua <jlease at hmc.psu.edu> wrote:

> Admins,
> 
> At Penn State Hershey we are considering alternate authentication methods for access to the SWEET module of eagle-i. We are trying to use CoSign or Shibboleth (they are similar). I would like to ask you a few questions to help me in this effort.
> 
> Do you know of any other institutions that have implemented Shibboleth? Are there any eagle-i features that aid in implementing alternate authentication methods? Do you have any other advice for setting up an alternate authentication method?
> 
> I noticed a configuration value eagle.identity.url that seemed like it could be something useful, but it is deprecated. Is that feature being replaced with something similar?