[Iplant-api-dev] Staging files at iPlant through the API

[Rion Dooley]

Hi Carol,

I’ve been working on this for you, but I don’t have an answer quite yet. I should have one for you after lunch. I’m sorry for the delay. You have my word that I will sort this out for you asap.

--
Rion




On Nov 27, 2013, at 8:56 AM, Lushbough, Carol <Carol.Lushbough at usd.edu<mailto:Carol.Lushbough at usd.edu>> wrote:

I was wondering if anyone can help me with the following problem:

We have a very simple workflow with the BioExtract Server that runs a tool on our cluster at USD and then attempts to stage its output file to iPlant through the API to use as input into a tool on lonestar, executed through the API.

Some accounts, including bioextract, are unable to create a directory in their home folder. A curl request such as:

curl -X PUT -vsku "<user>:<auth>" -d "dirName=ShinyNewDirectory&action=mkdir" https://foundation.iplantc.org/io-v1/io/<user>

receives a 403 HTTP response with the following body:

{
    "message": "The server understood the request, but is refusing to fulfill it",
    "result": null,
    "status": "error"
}

The behavior is the same whether authenticating with a password or token.


Carol Lushbough
Assistant Professor of Computer Science
University of South Dakota
605.677.6138

_______________________________________________
Iplant-api-dev Mailing List: Iplant-api-dev at iplantcollaborative.org<mailto:Iplant-api-dev at iplantcollaborative.org>
List Info and Archives: http://mail.iplantcollaborative.org/mailman/listinfo/iplant-api-dev
One-click Unsubscribe: http://mail.iplantcollaborative.org/mailman/options/iplant-api-dev/dooley%40tacc.utexas.edu?unsub=1&unsubconfirm=1

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.iplantcollaborative.org/pipermail/iplant-api-dev/attachments/20131127/3c8afea0/attachment.html