From fcoldren at mail.med.upenn.edu Wed Jun 25 12:50:03 2014 From: fcoldren at mail.med.upenn.edu (Faith Coldren) Date: Wed, 25 Jun 2014 12:50:03 -0400 Subject: [Eagle-i-admins] release 2.0MS3.07 Message-ID: Hi, Does release 2.0MS3.07 use the Integrated Semantic Framework? Best, Faith -------------- next part -------------- An HTML attachment was scrubbed... URL: From jlease at hmc.psu.edu Mon Jun 30 12:26:07 2014 From: jlease at hmc.psu.edu (Lease, Joshua) Date: Mon, 30 Jun 2014 16:26:07 +0000 Subject: [Eagle-i-admins] Authentication via Shibboleth Message-ID: 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? Thanks, Joshua Lease *****E-Mail Confidentiality Notice***** This message (including any attachments) contains information intended for a specific individual(s) and purpose that may be privileged, confidential or otherwise protected from disclosure pursuant to applicable law. Any inappropriate use, distribution or copying of the message is strictly prohibited and may subject you to criminal or civil penalty. If you have received this transmission in error, please reply to the sender indicating this error and delete the transmission from your system immediately. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jlease at hmc.psu.edu Mon Jun 30 12:30:10 2014 From: jlease at hmc.psu.edu (Lease, Joshua) Date: Mon, 30 Jun 2014 16:30:10 +0000 Subject: [Eagle-i-admins] eagle-i Documentation Source Message-ID: Admins, I am looking for the source of eagle-i documentation that is the most up to date. Can anyone point me in the right direction? Thanks, Joshua Lease *****E-Mail Confidentiality Notice***** This message (including any attachments) contains information intended for a specific individual(s) and purpose that may be privileged, confidential or otherwise protected from disclosure pursuant to applicable law. Any inappropriate use, distribution or copying of the message is strictly prohibited and may subject you to criminal or civil penalty. If you have received this transmission in error, please reply to the sender indicating this error and delete the transmission from your system immediately. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Daniela_Bourges at hms.harvard.edu Mon Jun 30 21:52:01 2014 From: Daniela_Bourges at hms.harvard.edu (Bourges, Daniela) Date: Mon, 30 Jun 2014 21:52:01 -0400 Subject: [Eagle-i-admins] eagle-i Documentation Source In-Reply-To: References: Message-ID: <15DF60A2-682E-4FBA-9C29-D66F9B01A0B1@hms.harvard.edu> Hi Joshua, the most up-to-date documentation is here: https://open.med.harvard.edu/wiki/display/eaglei/Documentation We recently deployed a new release centrally (3.0.2) but haven?t yet announced it publicly as we are still preparing the communication packages. However the documentation in the open.med site will remain largely unchanged. Let us know if you need pointers to specific topics. 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:30, Lease, Joshua wrote: > Admins, > > I am looking for the source of eagle-i documentation that is the most up to date. Can anyone point me in the right direction? > > Thanks, > Joshua Lease > > *****E-Mail Confidentiality Notice***** > This message (including any attachments) contains information intended for a specific individual(s) and purpose that may be privileged, confidential or otherwise protected from disclosure pursuant to applicable law. Any inappropriate use, distribution or copying of the message is strictly prohibited and may subject you to criminal or civil penalty. If you have received this transmission in error, please reply to the sender indicating this error and delete the transmission from your system immediately. > > _______________________________________________ > Eagle-i-admins mailing list > Eagle-i-admins at open.med.harvard.edu > https://open.med.harvard.edu/mailman/listinfo/eagle-i-admins From Daniela_Bourges at hms.harvard.edu Mon Jun 30 23:02:54 2014 From: Daniela_Bourges at hms.harvard.edu (Bourges, Daniela) Date: Mon, 30 Jun 2014 23:02:54 -0400 Subject: [Eagle-i-admins] Authentication via Shibboleth In-Reply-To: References: Message-ID: 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 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?