Songkick's API key should be under Canonical's control
Bug #1477496 reported by
Mark Tully
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Unity Songkick Scope |
Fix Committed
|
Undecided
|
Unassigned | ||
Bug Description
Currently, the API key being used for the Songkick scope is the one I applied for when initially developing the scope. This API key is owned by me rather than Canonical. Given that the requests come from a server controlled by Canonical, the API key being used should also be controlled by them.
Revision history for this message
| David Callé (davidc3) wrote | #1 |
| Changed in unity-scope-songkick: | |
| status: | New → Fix Committed |
Revision history for this message
| Bret Barker (noise) wrote | #2 |
To post a comment you must log in.
Being fixed server side with a key override. The one in the project can be replaced by an empty string or an "<insert your API key>" one.