In order to use the University of Minnesota's common login (and avoid another username/password to remember), we setup four parameters for each user within the i2b2 PM cell:
1. authentication_method (our custom method is called UMN but a new one could be added for another location) 2. authentication_webservice (location of the webservice - e.g. https://www.umn.edu/somewebservice) 3. authentication_webservice_method (the method to call within that webservice that validates the user) 4. authentication_key (unique key generated by the webservice so only trusted sites can call it) The webservice we created simply queries our common University login with the username/password supplied by the user. If success, return a 1, if fail, return a 0. We set the firstname, lastname, email, and username values within i2b2 and leave the password field blank. I don't recall what code needed to be changed under the i2b2 hood but I could find that out. I'd think something similar could be used for Babel as long as each site could provide a webservice that queries that site's central login service. Justin On Tue, Mar 25, 2014 at 3:37 PM, Dan Connolly <[email protected]> wrote: > Federated across which communities? > > Babel currently has a wrapper that manipulates the i2b2 database similar > to what you describe. But it requires users to maintain Yet Another > Password. > > The goal of using InCommon or the like is that once it's set up, if you > can authenticate to UTSW, babel takes UTSW's word that you're who you say > you are. > > -- > Dan > > ------------------------------ > *From:* Phillip Reeder [[email protected]] > *Sent:* Tuesday, March 25, 2014 1:46 PM > *To:* Thomas F Mish > *Cc:* [email protected]; Dan Connolly > *Subject:* Re: [gpc-informatics] #93: federated login using InCommon for > GPC services such as babel > > We federated an i2b2 client for a project down in Houston. We wrote a > small wrapper that added a username into i2b2 database and set the password > to be the session id. Then injected that into the i2b2 Ajax client > dynamically to log the person into i2b2. When the person logged out or > their season expired, it disabled the account. It could probably be > repurposed for this project. I'm not a technical shibboleth/incommon > federation expert though. > > Phillip > > Sent from my iPhone > > On Mar 25, 2014, at 1:31 PM, "Thomas F Mish" <[email protected]> wrote: > > Hi Dan, > > So, I've talked with one of our experts here at UW-Madison; > > > NameKEITH D HAZELTON > [email protected] > Phone(608) 262-0771, (608) 262-8874 > TitleSR INFO TECH ARCHITEC > DivisionINFORMATION TECHNOLOGY > DepartmentENTERPRISE INTERNET SERVICES > UnitARCHITECHTURE-GEN > Mailing address2172 Computer Sciences & Statistics > 1210 W Dayton St > Madison, WI 53706 > > Keith is knowledgable about InCommon and would be willing to talk with us > about its use with the http://babel.gpcnetwork.org/i2b2/webclient/website. > What do you think is the next step. Are there folks down at KUMC > that he could help? I'm unclear of the next step. If you give me the names > of the technical folk down there, I can try to get a technical phone call > together to take the next step. > > -TM > > > > On 3/25/2014 11:39 AM, GPC Informatics wrote: > > #93: federated login using InCommon for GPC services such as babel > --------------------------+----------------------- > Reporter: dconnolly | Owner: mish > Type: design-issue | Status: assigned > Priority: minor | Milestone: > Component: data-sharing | Resolution: > Keywords: | Blocked By: > Blocking: | > --------------------------+----------------------- > Changes (by dconnolly): > > * owner: dconnolly => mish > * status: new => assigned > > > Comment: > > Tom offers to find some contacts > > -- > Ticket URL: > <http://informatics.gpcnetwork.org/trac/Project/ticket/93#comment:1> > <http://informatics.gpcnetwork.org/trac/Project/ticket/93#comment:1> > gpc-informatics <http://informatics.gpcnetwork.org/> > <http://informatics.gpcnetwork.org/> > Greater Plains Network - Informatics > > > _______________________________________________ > Gpc-dev mailing list > [email protected] > http://listserv.kumc.edu/mailman/listinfo/gpc-dev > > > ------------------------------ > > UT Southwestern Medical Center > The future of medicine, today. > > _______________________________________________ > Gpc-dev mailing list > [email protected] > http://listserv.kumc.edu/mailman/listinfo/gpc-dev > >
_______________________________________________ Gpc-dev mailing list [email protected] http://listserv.kumc.edu/mailman/listinfo/gpc-dev
