Imported Google Group message.
Date:Thursday, 27 August 2015 18:30:05 UTC+1.
I was trying to figure out what happened to the tyk admin api key. Seems like the key has been renamed.
Tyk Admin API Key name is always suffix with the access_key (fcdd741b85da444f7208173c7ca0174d). But, at some point the key name has been changed (tyk-admin-api-5ae6165f-8507-496c-7440-41a5b4845ec3) and also this key is set to expire. I suspect tykdash changed it. Can you explain when this would happen?
127.0.0.1:6379> GET “tyk-admin-api-5ae6165f-8507-496c-7440-41a5b4845ec3”
127.0.0.1:6379> ttl “tyk-admin-api-5ae6165f-8507-496c-7440-41a5b4845ec3”
On Tue, Aug 25, 2015 at 2:32 PM, Martin Buhr [email protected] wrote:
Regarding Issue 1, Since the api access key is stored in in mongo db collection (tyk_analytics_users) I also restarted tykdash and expected it to be loaded.
Oh I see! I thought you were talking about portal developer users :-/
The dashboard user keys are stored in Redis when created. There was a reason for this, ages back when we put it together, I think it was to avoid hitting Mongo all the time when using the dashboard, redis is just faster. But they don’t reload, which I admit is an oversight - we assumed you wouldn’t restart redis
Might be worth looking into changing - can you raise a ticket in our GitHub repo so we can track it?