Getting the error "RallyRESTAPIError: 422 Action not allowed: invalid key" when trying to create a rally test
The code below works fine until I try it today:
...
tc_data = {'Description': 'Test Case Dummy', 'c_QATCPARAMSTEXT': 'GET|/users/$id[1]|||200|{"id":"$id","firstname":"$firstname","lastname":"$lastname","email":"$email","role":"$role"}|||||||DeleteUser;logout|||||login;CreateUser||{"user[email]":"$admin_email","user[password]":"$admin_password"};{"user[email]":"$standard_email","user[firstname]":"$standard_firstname","user[lastname]":"$standard_lastname","user[role]":"$standard_role","user[password]":"$standard_password"}|||||||||||||||||||||||||||||', 'Objective': '', 'LastBuild': '', 'TestFolder': '', 'Type': 'Acceptance', 'Method': 'Automated', 'Expedite': 'false', 'Name': 'Test Case Dummy'}
tc = self.rally.put('TestCase', tc_data)
...
It shows the error: "RallyRESTAPIError: 422 Action not allowed: Invalid key" and the test case could not be generated. This also happens when I try to create an assembly. However, the GET request works fine as usual.
This is similar to developers using java and C # Rally wrapper: .Net Rally.RestApi error "Action not allowed: Invalid key" when creating Rally test folder . Please, help!
source to share
This is a defect and Rally is working to fix it. In the meantime, a workaround that allegedly worked for the people who originally reported this is to use ApiKey instead of basic (username / password) authentication, Pyral 1.1.1 supports ApiKey. It assumes that you are on rally1.rallydev.com and not on sandbox.rallydev.com. ApiKey is not supported in sandbox.
source to share