We're trying to upload test cases and test results to our Rally project space using the Rally API.
We generated our first API key which behaves correctly, however, subsequent API keys that we're generating by other users don't have permissions to return the user story references which is stopping the loading of the test cases to Rally...
They're recognized, however, don't return a value?
Btw, All the keys we've generated have been given full permissions.
Can anyone shed any light on this or does anyone have any experience with this API/issue?
Without knowing a bit more about the code in use and the exact behavior you are seeing, it is difficult to say what may be occurring.
I have opened a case for you so we can get more specifics about what you are experiencing.
As Michael points out it is difficult to pin point your issue without additional detail. However the linked TEC article below from our knowledge base discuses some WS API issues that can result in some of the behavior you are reporting.
In a nutshell If the workspace scoping is not set in the API request the users default workspace set in their profile will be used. In many cases this results in either a permission problem or unexpected results because the target project or artifact does not exist in the defaulted workspace.
It should also be noted that "Full Permission" grants at the API key level do not extend outside the permissions already granted to the user within the application. Full permissions only applies to the CRUD API Actions available within the bounds of the users granted permissions.
How workspace scoping in the UI affects workspace scoping in WS API queries
Thanks for the response, we solved it, it was actually to do with the default workspace/project of the users trying to send cases/results... they hadn't selected a specific workspace/project.... Simple eh