[Iplant-api-dev] Staging files at iPlant through the API
Lushbough, Carol
Carol.Lushbough at usd.edu
Wed Nov 27 07:56:31 MST 2013
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.iplantcollaborative.org/pipermail/iplant-api-dev/attachments/20131127/09a94255/attachment.html
More information about the Iplant-api-dev
mailing list