Brocade Communications Systems 53-1001778-01 manual Configuring Http access

Page 40

3 SMI Agent security

FIGURE 10 Mutual authentication for indications

Configuring HTTP access

When HTTP access is disabled, only HTTPS access is available to the clients. The SMI-A server must be stopped to enable HTTP access, and must be running to disable HTTP access.

You must have Administrator privileges (Windows) or root/admin privileges (Linux, Solaris, and AIX) to enable or disable HTTP access. This option is disabled if you do not have the appropriate privilege.

1.Launch the Brocade SMI Agent Configuration Tool.

2.Click HTTP Access in the menu tree (see Figure 11).

The content pane displays the current setting, which is selected and unavailable. If the SMI-A server is not running, the Configuration Tool cannot determine whether HTTP access is enabled and so displays the default setting and not the current setting.

3.To change the HTTP access setting, click the button of the available option.

If HTTP access is already enabled, the Disable HTTP Access option is available. If HTTP access is already disabled, the Enable HTTP Access option is available.

4.Perform one of the following actions:

To enable HTTP access, ensure that the SMI-A server is stopped. Click the Stop Server button. To disable HTTP access, ensure that the SMI-A server is running. Click the Start Server button.

5.Click Apply.

24	Brocade SMI Agent User’s Guide
	53-1001778-01

Image 40

Contents Brocade SMI Agent Brocade Communications Systems, Incorporated Title Publication number Summary of changes Date Brocade SMI Agent User’s Guide Contents Chapter Brocade SMI Agent Configuration Chapter Mutual Authentication for Clients and Indications Index This chapter How this document is organizedSupported hardware and software Document conventions What’s new in this documentText formatting Identifies command syntax examples Key termsBrocade resources Additional informationOther industry resources Getting technical help FT00X0054E9Brocade SMI Agent support Support@brocade.comDocument feedback Overview Common Information Model CIMBrocade SMI-S Initiative Brocade SMI AgentBrocade SMI Agent Brocade SMI Agent User’s Guide Brocade SMI Agent Starting the SMI-AStop the Brocade SMI Agent Starting the SMI-A as a serviceStopping the SMI-A Service Location Protocol SLP support Stopping the SMI-A as a serviceSlptool commands SLP on Linux, Solaris, and AIXStarting SLP on Linux, Solaris, and AIX Stopping SLP on Linux, Solaris, and AIXSLP on Windows Installing SLP on WindowsStarting SLP on Windows Disable Http for security reasons Connection monitoringEnable multi-homed support For exampleBrocade SMI Agent Configuration About the Brocade SMI Agent Configuration ToolApply Launch the Brocade SMI-A Configuration Tool Launching the Brocade SMI Agent Configuration Tool WindowsReloading provider.xml on fabric segmentation Proxy connectionsAdding proxy connections Login failure status information Removing proxy connectionsAccess control Access control Login failure status messagesMapping an SMI-A user to a switch user Setting up default SMI-A user mapping Limitations of SMI-A user-to-switch user mapping SMI Agent securityMutual authentication setup Configuring mutual authentication for clientsConfiguring mutual authentication for indications Configuring Http access Mutual authentication for indicationsHttp access Importing client certificatesExporting server certificates SMI Agent security Configuring user authentication User authentication Encoding proxy connection details Encode proxy detailsSMI Agent service configuration and removal Configuring or removing the SMI Agent as a serviceConfigure Http and Https ports Port configurationConfiguring the Http and Https ports Configure ARR and eventing ports Configuring the ARR and eventing portsFabric Manager database server configuration Configure ARR and eventing portsFirmware download software locations configuration Configuring software locations for firmware downloadFile Path Configuring debugging options for Cimom Debugging and logging options configurationDebugging options for Cimom Configure debugging options for Cimom Debugging options for the providerConfiguring debugging options for the provider Dynamic UpdateConfiguring logging options for provider Logging options for the providerConfigure logging options Log file examplesCapture provider cache information Capturing information from the provider cacheSupport information collection Collect support informationCollecting support information XML dumpRunning an XML dump Cimom server configuration Configuring the Cimom serverConfiguring log file options Uncomment the following linesMutual authentication for clients IntroductionMutual authentication for indications Client configuration to use client certificatesEnabling mutual authentication for clients Enabling mutual authentication for indicationsClient.ind.truststore Clientind.cer Java -classpath SMIAgent/agent/wbem.jar Troubleshooting XmlerrorXmlerror Frequently Asked Questions General questionsHow do I collect diagnostic data from the Brocade SMI Agent? Does the SMI Agent have support for Https communication? On Linux Type the following command Open source software used in SMI-A AppendixSun Industry Standards Source License Source Code LicenseDistribution Obligations Inability to Comply DUE to Statute or Regulation Termination IBM Common Public License Grant of Rights Commercial Distribution OpenSLP License Bouncy Castle GNU Library General Public LicensePublic Domain Sun Binary Code License AgreementBrocade SMI Agent User’s Guide Supplemental License Terms Brocade SMI Agent User’s Guide Brocade SMI Agent User’s Guide 53-1001778-01 Sun Binary Code License Agreement Index Brocade SMI Agent User’s Guide