Brocade Communications Systems 53-1001778-01 manual Exporting server certificates

Page 42

3 SMI Agent security

FIGURE 12 Importing client certificates

3.Enter information for the client certificate to be used for mutual authentication for clients.

a.Type the path of the client certificate in the Certificate File Name field, or click Select File to browse for the file.

b.Type the alias name of the certificate in the Alias Name field.

4.Enter information for the client certificate to be used for mutual authentication for indications.

5.Click Apply.

The changes take effect when you restart the server. Click Start Server to restart the server.

Exporting server certificates

If you enable mutual authentication for clients or mutual authentication for indications, you can export the corresponding SMI-A server certificate to a file so the client can add the certificate to its TrustStore. This certificate will be used for authentication if mutual authentication is enabled.

If mutual authentication is enabled and if you do not export the SMI Agent server certificate, then the client keystore, truststore, and server certificates will be used for authentication.

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

1.Launch the Brocade SMI Agent Configuration Tool.

2.Click Export in the menu tree (see Figure 13).

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

Image 42

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 What’s new in this document Document conventionsText formatting Identifies command syntax examples Key termsAdditional information Brocade resourcesOther 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-AStarting the SMI-A as a service Stop the Brocade SMI AgentStopping 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 AIXInstalling SLP on Windows 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 WindowsProxy connections Reloading provider.xml on fabric segmentationAdding 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 servicePort configuration Configure Http and Https portsConfiguring 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 Debugging and logging options configuration Configuring debugging options for CimomDebugging 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 informationXML dump Collecting support informationRunning an XML dump Cimom server configuration Configuring the Cimom serverConfiguring log file options Uncomment the following linesMutual authentication for clients IntroductionEnabling mutual authentication for clients Mutual authentication for indicationsClient configuration to use client certificates 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