In case you aren't getting the expected behavior from the Authentication portion of the Commerce Solution, we've compiled a list of things to check. In this list, we take you through a generic configuration to make sure that Authentication is working correctly at each step. After getting it to work with the default settings, you can begin customizing RealServer for your site.

1. Use the latest version of RealPlayer 5.0.
   The Beta version of RealPlayer may not work with the Authentication features of RealServer. The released version is free, and it's available at http://www.real.com/products/player/index.html.

2. Install and test RealServer with non-secure content.
   Make sure that RealServer is serving non-secure content correctly.

   Note: If you're running RealServer on Windows NT as a service, make sure you have version 5.01 of the RealServer. If you don't, it's available at http://service.real.com/help/ library/servers.html.

3. Have some sample secure content available.
   Copy the entire folder named "secure.rm" from the commerce/content/secure directory into <BasePath>/secure (where <BasePath> is the directory specified by the BasePath setting in the configuration file). The new directory will be named <BasePath>/secure/secure.rm.

4. Be sure Authentication is "on".
   Authentication is activated by the nine Authentication settings in the configuration file (server.cfg). For testing purposes, use"basic" plugin, as specified by the AuthDBPlugin setting. Uncomment the settings, and use the default values for the first six settings, as shown:

   AuthAllowDuplicateIDs false
   AuthDBName c:realserverplugins
   AuthDBPlugin rn-ppv-basic
   AuthMode 1
   AuthPath secure
   Realm false

   AuthDBPassword
   AuthDBUserID
   AuthRegPrefix

   After changing the file, restart the RealServer.

5. Try to play some secure content using a new identity.
   Now that you've configured RealServer to use basic settings, a dialog box that asks you for a name and password should appear when you try to view secure content. Use a new, unregistered name. Because you have not yet authorized yourself, you'll be denied access to the clip.
   1. Start RealPlayer.
   2. On the RealPlayer File menu, choose Open Location.
   3. In the URL box, type "pnm://<realserver>:7070/secure/secure.rm" (without the quotation marks).
   4. The RealPlayer will show a username /password dialog box.
      
   5. Type your username and password, and click OK.
   6. The message "Authentication failed. Retry?" appears. If the error message does not appear, and the RealPlayer begins showing content, make sure the secure material is in the correct directory (see step 3).

6. Now give yourself access. For testing purposes, register yourself using the Administration page.
   1. In your web browser, type "http://<realserver>:7070/" (without the quotation marks).
   2. In the Username box, type "Admin" (without the quotation marks).
   3. In the Password box, type "letmein" if you accepted the default monitor password during Setup, or type the password you specified.
   4. On the Administration page, click the "User Authentication" link.
   5. Make up a new username and password. Click Submit.
   6. Click the Back button.
   7. Grant access to your clip (the URL starts at the BasePath, so it would be secure/secure.rm).
   8. Try to play the clip again using the new username.
   9. Use the new username that you authorized in item #6. Now that you've officially been given access, you should be able to see the clip. If you don't see the dialog box when you attempt to play the clip, it's probably because RealPlayer is still "open" and has saved your password. Locate the RealPlayer icon in the tool tray, right-click it, and choose Close. Now start RealPlayer again and try to view the clip.

7. Add the database.
   1. Follow the instructions in the "Setting up Data Storage" section of "Implementing Authentication" in Chapter 5 for ODBC compliance (Windows NT) or to set up the database application (UNIX).
   2. Edit the configuration file. Change AuthDBPlugin to "rn-ppv-odbc" (Windows) or "rn-ppv-msql" (UNIX) and change AuthDBName to the name of the database.

8. Add the CGI and HTML files.
   Place the supplied CGI files, named ppvdemo.exe (Windows NT) or ppvdemo.cgi (UNIX) in the Web server script folder. Customize the three supplied .html files (register.html, confirm.html, and authlink.html) as described in the .html files themselves.

9. That's it!
   Now that Authentication is working under the generic configuration, you can begin customizing RealServer to your unique needs.