Troubleshooting Authentication
If an aspect of Authentication is not working, use the steps below with
the supplied files to ensure that Authentication is working correctly in
its default configuration.
- Make sure your database is running and that appropriate access permissions
and paths have been set such that the RealServer can access the database.
- Start RealServer. If it is already running, stop and restart it. The
server must always be started after the database is started, and after
any changes are made to the database structure.
- Point your Web browser to the secure.ram link on the authlink.html
page. The RealPlayer starts and the message "Server alert: access
to secure content denied" appears. If the browser is able to immediately
receive media content or receives a database error, your RealServer is
unable to access your database. Check your permissions and restart the
server.
- Now point your browser to the "register" link. Your
RealPlayer plays a 0­second clip (one of the pnrv files located
in auth.rm) and your browser displays the register.html page.
If there is an error playing the clip, check the path in the auth.ram file
and make sure your RealServer is running and able to serve other clips
from the content directory. If the clip plays, but doesn't show the register.html
page, make sure your merged the correct path into your clip from the register.txt
file.
- Fill in a username on the register page and click Submit. Under Player-based
Authentication, your RealPlayer plays a 0-second clip (the register.rm
file) and your browser displays the confirm.html page. Under User-based
Authentication, your browser displays the confirm.html. If a CGI
error occurs, check the path to the CGI in your html files and check the
placement of the CGI on your Web server. If a RealPlayer "Error 14"
occurs, make sure your RealServer is able to serve other clips, make sure
the register.rm file is in the path identified in your .html, and make
sure the RealServer was started after the database. If the clip plays but
the confirm.html page does not appear, make sure you correctly merged the
correct path from register.txt into register.rm.
- Fill in a username in the confirm page and click Submit. You are returned
to the authlink.html page, and the secure content is now accessible.
If you aren't returned to the authlink.html page, check the address
given in confirm.html. If you are returned but are still given a
"Server alert" message, check the database to see whether you
were properly registered. The confirm.html will grant access to
a secure directory for Player-based authentication, and to a secure directory
and clip for User-based authentication.
- If you are able to register and unregister (filling in the same username
in the confirm.html page and pressing "Never Mind") and
are allowed and denied access to the clip in the secure.rm directory,
you have successfully installed Authentication and can further customize
your interface.
© 1997 RealNetworks, Inc.