API keys in HubProducer shouldn't be hardcoded about agorava-socializer HOT 4 CLOSED

Has this been fixed?

from agorava-socializer.

I can see no evidence, this is fixed in the codebase. Will open a bug in JIRA for that. If more people all use the same (Agorava's) API Key, if they do something stupid, e.g. too many API calls overflowing a target system, blame will be on US (the API Key owner) so we should allow people to override that key by using their own.

from agorava-socializer.

As I said in the ticket it's not fixed but has to be moved to Jira on
AGOVA-1 ticket.

Antoine Sabot-Durand

Le 17 juin 2012 à 23:09, Werner Keil
[email protected]
a écrit :

I can see no evidence, this is fixed in the codebase. Will open a bug in JIRA for that. If more people all use the same (Agorava's) API Key, if they do something stupid, e.g. too many API calls overflowing a target system, blame will be on US (the API Key owner) so we should allow people to override that key by using their own.

---

Reply to this email directly or view it on GitHub:
#3 (comment)

from agorava-socializer.

Just doing that

from agorava-socializer.