Hi, find it intriguing that nobody has replied to you.
I am no 😢 expert in coturn but may be able to help you.
First, you can enable the REST API support and then create the username password combinations yourself in your webrtc/signaling sockets server code as explained here,
But that doesn't prevent an attacker from mimicking your clients code and obtaining the credentials from your wewbrtc server, thus you'd need some form of validating the client-side user before the server issues those shared secret credentials, I am working on that part in my mind right now,
You could randomly challenge the client's user for information that only them could know, and only then allow the server to issue the credentials to the client. Read these two questions aand answers including the comments and you'll have it.
If somebody else emailed you directly with other suggestions, please share,
Thanks and best luck!