master/coturn
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add hash algorithm for key value to redis userdb schema

Browse Source
This commit is contained in:
Wuelber Castillo 2021-01-14 09:57:10 -06:00
parent e5d4e62dec
commit a767115055
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
turndb/schema.userdb.redis
View File

@ -6,9 +6,12 @@ has the following schema:
1) For the long-term credentials there must be keys 1) For the long-term credentials there must be keys
"turn/realm/<realm-name>/user/<username>/key" and the values must be "turn/realm/<realm-name>/user/<username>/key" and the values must be
the the hmackeys. For example, for the user "gorst", realm "north.gov" the hmackeys which is an md5 hash of "<username>:<realm-name>:<password>"
(See STUN RFC: https://tools.ietf.org/html/rfc5389#page-35).
For example, for the user "gorst", realm "north.gov"
and password "hero", there must be key "turn/realm/north.gov/user/gorst/key" and password "hero", there must be key "turn/realm/north.gov/user/gorst/key"
with value "7da2270ccfa49786e0115366d3a3d14d". and the value should be md5 hash of "gorst:north.gov:hero"
which will result in "7da2270ccfa49786e0115366d3a3d14d".
2) For the shared secrets (REST API), several key/value pairs 2) For the shared secrets (REST API), several key/value pairs
may be used (same as in SQL schema). The secrets are stored as members may be used (same as in SQL schema). The secrets are stored as members