I'm having trouble using redis as the user database with the longterm credential mechanism and plain passwords. Is it a strict requirement for me to also set keys? Specifically, COTURN is giving me:
Jun 26 18:18:55 newton turnserver: 38: session 000000000000000001: realm <XXXXX> user <cf151d93>: incoming packet message processed, error 401: Unauthorised
Jun 26 18:18:55 newton turnserver: 38: check_stun_auth: Cannot find credentials of user <cf151d93>
Background:
I have an external service running which is adding auto-expiring credentials to redis for clients to use. The TURN credentials are short lived (a few hours) and highly variable. Currently, my program just generates and inserts them without using turnadmin to generate a key at all. Using the turnutils_uclient, I can't seem to authenticate. I can confirm that the credentials exist in the redis database, and it seems like coturn is successfully connected to redis. For each user, I'm adding a single key/value, of the format
turn/realm/XXXXX/user/cf151d93/password 9406d2
If possible, I'd significantly prefer to avoid having to use the turnadmin to generate keys, as redis in this case is highly restricted and credentials are short-lived.