Does anyone's SWORDv2 implementation use API keys (negotiated via OAuth, maybe?) rather than HTTP Basic Authentication (username/password) in conjunction with a TLS connection?
In all of my testing I'm using HTTPS to send passwords securely, but supporting API keys would be nice. Thanks, Phil p.s. This came up in a meeting yesterday and I just entered the suggestion at https://redmine.hmdc.harvard.edu/issues/3208 after some discussion at http://irclog.iq.harvard.edu/dvn/2013-08-01 -- Philip Durbin Software Developer for http://thedata.org http://www.iq.harvard.edu/people/philip-durbin ------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk _______________________________________________ sword-app-tech mailing list sword-app-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sword-app-tech
