After Helix Universal Server has authenticated user access, it can check whether the user has permission to view specific clips or directories. You can use this information for applications such as pay-per-view. Permission information is stored in a separate database, and this appendix describes the data storage methods that you can use with the authentication feature.
To authenticate visitors, the Helix Universal Server stores user IDs and passwords or client IDs, and their associated access permission information. When a client tries to access a clip, the Helix Universal Server looks up this information to see whether the client or visitor is authorized to view the clip. The information can be stored in either a series of text files or in a database. Templates for common databases are installed during installation.
This section describes the methods for storing user name and password data. Templates for common databases are created during installation, that correspond to the database types listed in "Supported Database Types".
The default configuration uses the text file storage method to provide storage
for all default realms. The following directories contain the text files which
store data. The center letter indicates the authentication protocol: r is for
RealSystem 5.0, b is for Basic.
The following table describes the contents of these directories.
The actual data storage text files do not exist when Helix Universal Server is first installed. They are created when authentication is in use, and secure content is first requested. When Helix Universal Server creates the file structure, it creates the ppvbasic.txt file. Helix Universal Server looks for this file the second and subsequent times you start it. If the file does not exist, it recreates the directory structure.
| Warning! Do not delete the ppvbasic.txt file! If you delete the ppvbasic.txt file, Helix Universal Server will rewrite the directories and erase their prior content. |
The files in this directory are named username, where username is the user
name. This directory contains one file per registered user. The first line of each
file has the following format and is different than subsequent lines in the file:
password;uuid;uuid_writeable |
| Field | Description |
|---|---|
password |
When user authentication is in use, this stores the password. Otherwise shows an asterisk (*). Passwords are encrypted. See "Using the Password Tool". |
uuid |
In player validation, stores playerID. In user authentication, an asterisk (*) appears in this field. |
uuid_writeable |
A flag set and used by Helix Universal Server:0playerID is in database1record created, but playerID is not yet registered |
The second and subsequent lines of each file have the following format. For further detail on allowable values in each field, see table "Permission Types":
url;url_type;permission_type;expires;debitted_time |
The example file, user1, has the following content, when player validation is in use:
*;00001d00-0901-11d1-8b06-00a024406d59;0 |
Note:
If you manually edit the files, be sure that any blank or
unused fields use an asterisk (*) as a placeholder. Do not use a
space for a placeholder.
|
The files in this directory are given the names of the unique client IDs from
the registered clients, one per registered user. Each file contains only the name
of the associated user name. For example, a file such as 00001d00-0901-11d1-
8b06-00a024406d59 contains the name of the user, user1.
This directory contains two files: reglog.txt and accesslog.txt.
Each line of reglog.txt represents the result of an attempt to register a visitor. This file has the following format:
status;userid;uuid;IP;register_time;url_redirect |
Each line of accesslog.txt describes the result of an attempt to view a clip. This file is not created until authentication is enabled and the first user attempts to connect:
status;userid;uuid;ip;url;access_type;permission_on;start_time;end_time;total_time; |
| Field | Description |
|---|---|
status |
Result of user's attempt to connect: 0access to clip granted1denied |
userid |
Unique name of up to 50 characters. |
uuid |
Stores player ID. |
ip |
IP address from which user is attempting to connect. |
url |
Secured clip user is attempted to access. |
access_type |
Permission type associated with access. See the table "Permission Types" for values. |
permission_on |
Permission type associated with URL: 0file (individual clip)1directory2none |
start_time |
Time/date clip started playing. |
end_time |
Time/date clip stopped playing. |
total_time |
Total time clip played. |
why_disconnect |
Reason for disconnection:0client disconnected voluntarily1server access expired |
Used only in player validation, the redirect directory contains files named after URLs that are restricted from unauthorized users. Within each file is the alternate URL to which Helix Universal Server sends the user if he or she tries to click the restricted URL. If no files are present in this directory, and the user attempts to click a URL to which he or she has not been given access, the user receives an error message.
Because certain characters that appear in URLs are illegal in file names, Helix Universal Server requires a substitution for these illegal symbols.
| Character | Replacement Sequence |
|---|---|
/ |
+2f |
\ |
+2b |
+ |
+5c |
For example, the URL Secure/TopSecret.rm would be converted to
Secure+2fTopSecret.rm. The URL within each file, however, is represented
normally.
This section describes the structure of the database templates included with Helix Universal Server. To set up the database, see "Setting Up Other Types of Data Storage". The database templates include five tables:
Gives the list of user names and passwords.
Linked to the users table through the userid, this identifies the specific clips or directories and the type of access for each.
The register_log table is used only if player validation is in use (indicated by
UseGUIDValidation=True).
The redirect table is only used in player validation.
Used by the commerce feature to show which secure content has been accessed.
| Field | Description |
|---|---|
status |
Result of user's attempt to connect:0access to clip granted1denied |
userid |
Unique name of up to 50 characters. |
uuid |
Stores player ID. |
ip |
IP address from which user is attempting to connect. |
url |
Secured clip user is attempted to access. |
permission_type |
Permission type associated with access. See the table "Permission Types" for values. |
permission_on |
Permission type associated with url:0file (individual clip)1directory2none |
start_time |
Time/date clip started playing. |
end_time |
Time/date clip stopped playing. |
total_time |
Total time clip played. |
why_disconnect |
Reason for disconnection:0client disconnected voluntarily1server access expired |
Support for two types of databases is included.
| To set up your Windows computer for ODBC compliance: |
You must now tell Helix Universal Server where to find your database.
| To set up the supplied database application on UNIX: |
./msql2d & |
./msqladmin create databasename |
databasename will need to match the database cited in the Databases list.
.msql -h localhost databasename < |
|
|
© 2002 RealNetworks, Inc. All rights reserved.
For more information, visit RealNetworks Click here if the Table of Contents frame is not visible at the left side of your screen. |