The Users.xm file is located at the root level of the RootInstall/conf directory. Edit this file to identify Adobe Media Server administrators and set their access permissions. Edit this file to set permissions for Administration API calls to Adobe Media Administration Server.

To see the element structure and default values, see the Users.xml file installed with Adobe Media Server in the RootInstall/conf/ directory.

AdminServer

Container element.

The HttpCommands container nested within the AdminServer container configures the access level to Adobe Media Administration Server.

The Administration Service is separate from Adobe Media Server. When administrators use the Administration Console to connect to Adobe Media Server, they are connecting to Adobe Media Administration Server, which in turn connects to the server.

Contained elements

Allow (HTTPCommands)

Lists the Adobe Media Administration Server commands that the administrator can access using HTTP. You can authorize an administrator to use multiple HTTP commands for access by creating a comma-separated list of the commands. The value All authorizes the administrator to use all HTTP commands. However, Adobe does not recommend this usage as it creates a security risk.

Example

 <Allow>foo.yourcompany.com,adobe.com,10.60.1.133,10.60</Allow>

See also

Allow (User)

Lists the specific hosts from which an administrator can connect to Adobe Media Administration Server. The administrator can only connect to the server from those hosts specified in this Allow element. You authorize the administrator’s access by creating a comma-delimited list of the accessible host names or domain names and/or full or partial IP addresses. Whenever possible, use the IP addresses in the Allow element to improve the server’s performance when processing connection requests.

Example

 <Allow>foo.yourcompany.com, adobe.com, 10.60.1.133, 10.60</Allow>

See also

Deny (HTTPCommands)

Adobe Media Server uses two elements named Deny: the Deny element in the User container and the Deny element in the HTTPCommands container.

This Deny element lists the Adobe Media Administration Server commands that an administrator cannot use through HTTP.

You can deny an administrator the use of multiple HTTP commands to access the Administration Service by creating a comma-separated list of those HTTP commands.

Example

 <Deny>Deny,Allow</Deny>

See also

Deny (User)

Adobe Media Server uses two elements named Deny: the Deny element in the User container and the Deny element in the HTTPCommands container.

This element lists those hosts from which the administrator is not authorized to connect to Adobe Media Administration Server. You restrict the administrator’s access by creating a comma-delimited list of those host names or domain names and/or (full or partial) IP addresses.

Example

This example lists the computers sending connection requests that Adobe Media Administration Server will not accept.

 <Deny>foo.yourcompany.com,adobe.com,10.60.1.133,10.60</Deny>

See also

Enable

This element enables or disables the use of HTTP requests to execute administrative commands.

Setting this element enables HTTP requests to execute administrative commands. To disable administrative access through the use of HTTP requests, do not set this element.

Example

 <Enable>true</Enable>

See also

HTTPCommands

Container element.

This section contains the settings for those Adobe Media Administration Server commands that can be accessed through HTTP. The default value is ping. Specify each Administration API that may be called over HTTP in a comma-delimited list. When finished, restart the server.

Contained elements

Order (HTTPCommands)

Adobe Media Server uses two Order elements: one in the HTTPCommands container and another in the User container.

Specifies the order in which to evaluate the Deny and Allow commands.

Example

The sequence Deny, Allow means the HTTP command is allowed if the command is in the Allow list of commands or not in the Deny list.

 <Order>Deny,Allow</Order>

The sequence Allow, Deny means the HTTP command is allowed if it is in the Allow list of commands and not in the Deny list.

 <Order>Allow,Deny</Order>

See also

Order (User)

Adobe Media Server uses two Order elements: one in the HTTPCommands container, and the other in the User container.

Specifies the sequence in which Adobe Media Server evaluates the Allow and Deny elements for an administrator.

Example

The default sequence Allow, Deny means that administrative access is allowed unless the user is specified in the Allow list of commands and not in the Deny list:

 <Order>Allow,Deny</Order>

The alternative sequence Deny, Allow means that administrative access is allowed unless the user is specified in the Deny list of commands and not specified in the Allow list.

 <Order>Deny,Allow</Order>

See also

Password

A salted hash of the password for vhost administrators.

Passwords cannot be empty strings (""). Passwords are usually encrypted.

Example

 <Password>e206a5e1b52dcb4eaf024ca6adbe321b86cf0079bb747b78134ddaf8375e10aff905da0b28e84c5a</Password>

See also

PasswordPolicy

You can use PasswordPolicy element to enable or disable minimum password length policy.

Example

<Root><PasswordPolicy enable="false"></PasswordPolicy></Root>

Root

Container element.

The Root element is a container for all the other elements. If the Users.xml file resides under a virtual host (to define administrators for that virtual host), then this tag must have its name attribute set to the name of the virtual host under which it resides.

Example

 <Root name="_defaultVHost_">

User

This element identifies an administrator of the server.

You can identify multiple administrators of a virtual host by creating a profile for each administrator.

Example

Use the name attribute to identify the login name of a Adobe Media Server administrator:

 <User name="jsmith"></User>

See also

UserList

Container element.

The UserList element defines and holds information about server administrators.

Contained elements

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy