XMDS register will register clients with non-unique ID
Bug #316438 reported by
Alex Harrington
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Xibo |
Fix Released
|
High
|
Dan Garner |
Bug Description
When calling the XMDS register method, persistent calls with identical options generates multiple displays with the same ID.
Contents of my display table:
Related branches
lp:~dangarner/xibo/xibo-server
- Dan Garner: Pending requested
Changed in xibo: | |
assignee: | nobody → dangarner |
Changed in xibo: | |
status: | New → Fix Committed |
Changed in xibo: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I have a theory on this. The DB defines license as varchar(32). I expect I'm returning something longer than 32 characters, in which case the comparison fails each time.
Possible solutions. I could shorten my MD5, but this leads to possible collisions between clients.
Increase the length of the license field in the display table.
I could hash on something different to shorten the MD5 by implication.
However, perhaps xmds should enforce this limit somehow.