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
Just a quick update, since the last post was about the quietness of the
list. We are still actively using SWORD to deposit content to Connexionx (
cnx.org). It just works, so we haven't had much traffic on the list!
Kathi
On Thu, Aug 1, 2013 at 8:02 AM, Philip Durbin
On Thu, Aug 1, 2013 at 10:07 AM, Philip Durbin
philip_dur...@harvard.edu wrote:
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?
It looks like Richard asked a similar
Hi Phil,
On 28 June 2013 22:05, Philip Durbin philip_dur...@harvard.edu wrote:
On Thu, Jun 27, 2013 at 10:53 AM, Philip Durbin
philip_dur...@harvard.edu wrote:
Before the jar gets published, I believe I may have found a bug here:
Hi Phil,
On 23 July 2013 18:32, Philip Durbin philip_dur...@harvard.edu wrote:
On Wed, Jul 17, 2013 at 11:14 AM, Philip Durbin
philip_dur...@harvard.edu wrote:
1. Am I doing it wrong by using the col-uri to both create the study
and upload example.zip?
After discussing this at
Hi Phil,
Having one of my period re-sync's with the mailing list :)
p.s. I'm growing concerned that this mailing list is so quiet (and
only admins can see the number of people subscribed). Have people
moved on from SWORD to some other standard? If so, which one?
I just checked - there are
