banner art

Using the WMS Anonymous User Authentication plug-in

If you want users to be able to access content without being prompted for a user name or password, you can enable the WMS Anonymous User Authentication plug-in. When a user attempts to connect to the Windows Media server, the plug-in uses the Windows user account that you specified in the plug-in properties to authenticate the user.

By default, the user account specified in this plug-in is WMUS_servername. If you are using the WMS NTFS ACL Authorization plug-in with the WMS Anonymous User Authentication plug-in, you must provide that the WMUS_servername account with read permissions for any files and folders that will be streamed from a publishing point. If you want to use another anonymous user account that already has the necessary rights and permissions, you can change the user account in this plug-in from the default value to the user account of your choice.

When this plug-in is enabled it allows anonymous users to connect to your server. You can restrict the content that anonymous users can access by enabling an authorization plug-in. The authorization plug-in enables you to set different access control policies for content. For example, you could allow users to access only certain content in a publishing point by using the WMS NTFS ACL Authorization plug-in.

This plug-in can be enabled on a single publishing point on your server. By setting the appropriate access control lists (ACLs) for your content folders, you can ensure that the account used by this plug-in can only access certain content. An example of this situation is an Internet site with both free and subscription-based digital media content.

Note Image Note

Related topics


© 2005 Microsoft Corporation. All rights reserved.

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.