Instead of letting every user choose their own user name, you can '''tie Thingy users to HTTP users''' -- that means that HTTP authentication (performed by your web server) dictates the Thingy user name of the user who has logged in via HTTP.
| | 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.
|
; ; <code>0</code>: 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 for users who are not HTTP-authenticated when using this setting.)
; ; <code>1</code>: Restricted access: See [[Restrict access to your Thingy]].
; ; no value (unset): Default behavior: Users can set their own user name on the ''Preferences'' page in Thingy.
| | ; ; <code>0</code>: '''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.)
; ; <code>1</code>: '''Restricted access:''' See [[Restrict access to your Thingy]].
; ; ''unset'': '''Default behavior:''' Users can set their own user name on the ''Preferences'' page in Thingy.
|