Cisco 11503 Administration Guide - Page 266

Parsing the XML Code Chapter 7 Using an XML Document to Configure the CSS • A secure SSL connection, use the global configuration no restrict secure-xml command. For example, enter: (config)# no restrict secure-xml The CSS listens on port 443 for a secure connection request. The client application can use SSL v2/3 or v3. However, the CSS performs all negotiations using SSL v3. The CSS requires a Secure Management license key to negotiate a secure connection using SSL strong encryption. Without the key, the CSS uses SSL weak encryption. To reset the default behavior to deny the transfer of XML configuration files through a secure connection, use the global configuration restrict secure-xml command. For example, enter: (config)# restrict secure-xml Parsing the XML Code After you complete the XML file, parse the code to ensure that it is syntactically correct. One easy way to parse XML code is to open the XML file directly from Microsoft Internet Explorer. Syntax errors are flagged automatically when the file is loaded. If an error occurs, review your XML code and correct all syntax errors. Publishing the XML Code to the CSS The completed XML file is remotely published (uploaded) to the HTTP server in the CSS from the external network management workstation by using an HTTP PUT method. The HTTP PUT method uses the IP address of the CSS as the destination URL where you want to publish the XML file. Note When you configure TACACS+ on a CSS, the CSS does not authorize scripts through the TACACS+ server. Because the CSS transforms all XML commands into scripts, the CSS also does not authorize XML commands through the TACACS+ server. Cisco Content Services Switch Administration Guide 7-6 OL-5647-02