[WOOKIE-206] SharedDataKey not kept unique internally

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 0.9.0
• Fix Version/s: 0.9.1
• Assignee: Scott Wilson
• Reporter: Scott Wilson
• Created: 15/Apr/11 10:47
• Updated: 25/Aug/11 15:11
• Resolved: 25/Aug/11 15:10

Description

In earlier versions of Wookie, we had an "external" shared data key and an "internal" shared data key. The internal version was a hash of the external key + API key + Widget URI. This was to prevent collisions between contexts used in multiple sites.

However, this seems to have disappeared at some point and now the sharedDataKey is simply persisted as-is. This means that, if you have multiple Wookie-enabled sites which reuse simple shared data keys (e.g. "1") then the widgets will use the same shared data.

To recreate this problem, configure Wookie with two API keys. Instantiate a chat widget with the same Shared Data Key (e.g. "1") but a different API key. Note that the chat is synchronized across both widgets