TubeStudio Authentication

TubeStudio About TubeStudio TubeStudio Requirements TubeStudio Installation Instructions Upgrading TubeStudio Getting Started TubeStudio Basics Getting Around Adding Videos Managing Sites Video Admin Adding Videos Bulk Importing Sites Admin Managing Sites Managing Channels Publishing Rules Site Configuration Users Admin User Admin User Features Authentication Methods Configuration Admin Configuration Admin Site Specific Configuration SEO Links Authentication Methods Template Admin Adding Skins Managing Skins All About Templates Extending and Customizing Template Functions display_list_videos display_search_results display_favorites display_favorite_link display_comments display_tag_cloud display_news print_page_numbers Misc. Admins Support Admin Thumbnail Settings Feedback Admin Cleanup & Maintenance Logs Admin News & Notifications Mailing Admin Troubleshooting Video Importing Site Licenses Expired License TubeStudio Extras coming soon...

TubeStudio provides a few default authentication methods. Users can be authenticated off of the internal database, an external NATS system, an external database, or through the HTTP headers ( your current mysql_auth, httpasswd,ext. setup). Below are the various settings and their descriptions for authenticating users.

These settings can be edited globally for all sites on the Configuration Admin or site specific in the site configuration.

Internal Authentication

This is the default authentication method for TubeStudio. All user data is stored in the local database and inserted when a user goes through the signup process. When using this method nothing else needs to be done by you.

External through HTTP Headers

Select his option if you use an external authentication system such as mysql auth or httpasswd files.

External through NATS

Selecting this method will use the NATS database for authenticating users. This option is only intended for NATS program owners and not affiliates. All login attempts will always refer to the external database for the correct username and password. Be sure to choose the correct version for your NATS install (v3 or v4).

If you are using this option then you will also need to fill in the values for:

• NATS_AUTH_HOST
  • Hostname for your NATS database
  • e.g. "localhost"
• NATS_AUTH_DB
  • Database name your NATS database
  • e.g. "my_nats_database"
• NATS_AUTH_USER
  • Username for your NATS database
• NATS_AUTH_PASS
  • Password for your NATS database
• NATS_AUTH_SITEID
  • Password for your NATS database

If you TubeStudio and NATS installations are on different servers, be sure to enter the correct hostname and make sure that the database allows the external communication through the username and password provided. It is recommended that you set up a new username and password that only has SELECT privileges on the member tables.

External through Other Database

Selecting this method will use a generic external database for authenticating users. All login attempts will always refer to the external database for the correct username and password.

If you are using this option then you will also need to fill in the values for:

• OTHER_AUTH_HOST
  • Hostname for your other database
  • e.g. "localhost"
• OTHER_AUTH_DB
  • Database name your other database
  • e.g. "my_database"
• OTHER_AUTH_USER
  • Username for your other database
• OTHER_AUTH_PASS
  • Password for your other database
• OTHER_AUTH_MISC_QUERY
  • A miscellaneous query that helps identify the user.
  • You MUST include the preceding "AND"
  • e.g. "AND siteid=2"
• OTHER_AUTH_TABLE
  • Table name of where to find your external users
  • e.g. "members"
• OTHER_AUTH_USER_FIELD
  • The username field in your external table
  • e.g. "user"
• OTHER_AUTH_PASS_FIELD
  • The password field in your external table
  • e.g. "pass"

If you TubeStudio installation and other database are on different servers, be sure to enter the correct hostname and make sure that the database allows the external communication through the username and password provided. It is recommended that you set up a new username and password that only has SELECT privileges on the member's table.