Bug 1094090

Summary: [Regression] TMX import/export blocked by api not providing user key
Product: [Retired] Zanata Reporter: Damian Jansen <djansen>
Component: Component-APIAssignee: Patrick Huang <pahuang>
Status: CLOSED CURRENTRELEASE QA Contact: Damian Jansen <djansen>
Severity: high Docs Contact:
Priority: high    
Version: developmentCC: zanata-bugs
Target Milestone: ---   
Target Release: 3.4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 3.4.0-SNAPSHOT (git-server-3.3.1-266-ga1bc59b) Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-17 06:39:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1088122    

Description Damian Jansen 2014-05-05 03:58:41 UTC
Description of problem:
With the rate limit change came a behavioural change for rest requests - the api key is required.
This did not get updated for the tmx import/export features of Zanata and results in a 401.

Version-Release number of selected component (if applicable):
Dev

How reproducible:
Easy always

Steps to Reproduce:
1. Go to any project version
2. select a language and press export to tmx

or

1. As admin, go to Administration > Translation Memory
2. Create or select a TM entry
3. Press the import button, select a file, press import

Actual results:
401 Not Authorized

Expected results:
If the user has a key, this should not appear.

Additional info:
The tm export shows the "key required" error, but the TM import does not.

Comment 1 Patrick Huang 2014-05-06 03:37:30 UTC
https://github.com/zanata/zanata-server/pull/433

Comment 2 Damian Jansen 2014-05-07 04:01:17 UTC
Verified