Instead of letting every user choose their own user name, you can tie Thingy user names to HTTP user names – that means that HTTP authentication (performed by your web server) dictates the Thingy user name of the user who has logged in via HTTP.
Set the following environment variable in your web server configuration to configure this behavior:
- THINGY_RESTRICTED
0- Full access, use HTTP user name: The user name entered during HTTP authentication dictates the user name used in Thingy. Users can still change their other settings on the Preferences page. (Note that Thingy's behavior is undefined if no HTTP authentication has actually taken place.)
1- Restricted access: See Restrict access to your Thingy.
- unset
- Default behavior: Users can set their own user name on the Preferences page in Thingy.