Closed
Bug 905390
Opened 12 years ago
Closed 11 years ago
restrict api to specific products
Categories
(Input Graveyard :: Submission, defect)
Input Graveyard
Submission
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: willkg, Assigned: willkg)
References
Details
(Whiteboard: u=dev c=api p= s=input.2013q3)
We should restrict the api to specific products and channels. This does two things:
1. prevents (ab)use of the api for nefarious purposes. e.g. FirefoxSUX as a product
2. normalizes the data so we don't end up with "firefox", "Firefox", "FIREfox", "FIREFOX"
I don't want to do a ForeignKey from Response to Product tables. I'd rather have a Product table that lists the appropriate product name and list of appropriate channels and have the API do a check against that table explicitly to validate the data.
Anyhow, this is probably a good idea to do sooner rather than later.
Assignee | ||
Comment 1•12 years ago
|
||
Should probably figure this out in 2013q3.
Whiteboard: u=dev c=api p= s=input.2013q3
Assignee | ||
Comment 2•11 years ago
|
||
The current set of products in the table.
MariaDB [fjord]> select distinct product from feedback_response;
+---------------------+
| product |
+---------------------+
| Firefox |
| Firefox for Android |
| Firefox OS |
| |
+---------------------+
4 rows in set (0.37 sec)
MariaDB [fjord]>
I'll tweak the API code to restrict to those three.
Assignee: nobody → willkg
Assignee | ||
Comment 3•11 years ago
|
||
PR: https://github.com/mozilla/fjord/pull/138
I thought about restricting channels, but I'm less sure I know what the actual list of channels is plus no one is including channel information, yet. So I only restricted products. Tweaking the title accordingly.
Summary: restrict api to specific products, channels → restrict api to specific products
Assignee | ||
Comment 4•11 years ago
|
||
Landed in master in https://github.com/mozilla/fjord/commit/96afa74
We don't push on Fridays, so I'll wait to push this to prod on Monday.
Status: NEW → ASSIGNED
Assignee | ||
Comment 5•11 years ago
|
||
LANDED AND PUSHED!
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•8 years ago
|
Product: Input → Input Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•