Brocade Communications Systems 53-1001778-01 manual Client.ind.truststore Clientind.cer

Page 65

Client configuration to use client certificates

4

•.client.ind.truststore

•clientind.cer

There are three ways to configure a WBEM client to use a client certificate with the SMI-A:

•using a property file

•using system property values when invoking the WBEM client

•using a WBEM client listener program (mutual authentication for indications only)

Configuring a client to use client certificates using a property file

1.Create a WbemClient.properties file, which contains information for the configuration of the client keystore and truststore.

For example, if the SMI-A is installed under D:\smiagent, the contents of the WbemClient.properties file should be as follows.

Mutual authentication for clients:

javax.net.ssl.keyStore=D:/smiagent/agent/client/.client.keystore

javax.net.ssl.keyStorePassword=SSLclient

javax.net.ssl.trustStore=D:/smiagent/agent/client/.client.truststore

javax.net.ssl.trustStorePassword=trustSSLclient

Mutual authentication for indications:

wbem.indications.keyStore=D:/smiagent/agent/client/.client.ind.keystore

wbem.indications.keyStorePassword=SSLindication

wbem.indications.trustStore=D:/smiagent/agent/client/.client.ind.truststore

wbem.indications.trustStorePassword=trustSSLindication

Note that both the javax.net.* properties and the wbem.indications.* properties can be specified in the same WbemClient.properties file.

2. Modify the CLASSPATH environment variable to reference this file.

The CLASSPATH should contain only the path to the directory where the file is present and not the path to the file itself. For example, if the WbemClient.properties file is located at C:\SMIAgent\agent, then the CLASSPATH environment variable should be:

C:\SMIAgent\agent

Configuring a client to use client certificates using system property values

Pass the required system properties as jvm parameters on the command line, using the -D option as follows.

Mutual authentication for clients:

java -classpath <SMIAgent>/agent/lib/wbem.jar

-Djavax.net.ssl.keyStore=<SMIAgent>/agent/client/.client.keystore -Djavax.net.ssl.keyStorePassword=SSLclient -Djavax.net.ssl.trustStore=<SMIAgent>/agent/client/.client.truststore -Djavax.net.ssl.trustStorePassword=trustSSLclient

clientprogram

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

Image 65

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 How this document is organized This chapterSupported hardware and software Text formatting What’s new in this documentDocument conventions Key terms Identifies command syntax examplesOther industry resources Additional informationBrocade resources FT00X0054E9 Getting technical helpSupport@brocade.com Brocade SMI Agent supportDocument feedback Common Information Model CIM OverviewBrocade SMI Agent Brocade SMI-S InitiativeBrocade SMI Agent Brocade SMI Agent User’s Guide Starting the SMI-A Brocade SMI AgentStopping the SMI-A Starting the SMI-A as a serviceStop the Brocade SMI Agent Stopping the SMI-A as a service Service Location Protocol SLP supportSLP on Linux, Solaris, and AIX Slptool commandsStopping SLP on Linux, Solaris, and AIX Starting SLP on Linux, Solaris, and AIXStarting SLP on Windows Installing SLP on WindowsSLP on Windows Connection monitoring Disable Http for security reasonsFor example Enable multi-homed supportAbout the Brocade SMI Agent Configuration Tool Brocade SMI Agent ConfigurationApply Launching the Brocade SMI Agent Configuration Tool Windows Launch the Brocade SMI-A Configuration ToolAdding proxy connections Proxy connectionsReloading provider.xml on fabric segmentation Removing proxy connections Login failure status informationAccess control Login failure status messages Access controlMapping an SMI-A user to a switch user Setting up default SMI-A user mapping SMI Agent security Limitations of SMI-A user-to-switch user mappingConfiguring mutual authentication for clients Mutual authentication setupConfiguring mutual authentication for indications Mutual authentication for indications Configuring Http accessImporting client certificates Http accessExporting server certificates SMI Agent security Configuring user authentication User authentication Encode proxy details Encoding proxy connection detailsConfiguring or removing the SMI Agent as a service SMI Agent service configuration and removalConfiguring the Http and Https ports Port configurationConfigure Http and Https ports Configuring the ARR and eventing ports Configure ARR and eventing portsConfigure ARR and eventing ports Fabric Manager database server configurationConfiguring software locations for firmware download Firmware download software locations configurationFile Path Debugging options for Cimom Debugging and logging options configurationConfiguring debugging options for Cimom Debugging options for the provider Configure debugging options for CimomDynamic Update Configuring debugging options for the providerLogging options for the provider Configuring logging options for providerLog file examples Configure logging optionsCapturing information from the provider cache Capture provider cache informationCollect support information Support information collectionRunning an XML dump XML dumpCollecting support information Configuring the Cimom server Cimom server configuration Uncomment the following lines Configuring log file optionsIntroduction Mutual authentication for clientsClient configuration to use client certificates Mutual authentication for indicationsEnabling mutual authentication for clients Enabling mutual authentication for indicationsClient.ind.truststore Clientind.cer Java -classpath SMIAgent/agent/wbem.jar Xmlerror TroubleshootingXmlerror General questions Frequently Asked 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 Appendix Open source software used in SMI-ASource Code License Sun Industry Standards Source LicenseDistribution Obligations Inability to Comply DUE to Statute or Regulation Termination IBM Common Public License Grant of Rights Commercial Distribution OpenSLP License GNU Library General Public License Bouncy CastleSun Binary Code License Agreement Public DomainBrocade 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