Brocade Communications Systems 53-1001778-01 manual Setting up default SMI-A user mapping

Page 36

3 Access control

The value in the Status column changes from Not Persisted to Persisted, which means the values are persisted to the provider.xml configuration file.

Setting up default SMI-A user mapping

You can set up a default mapping that applies to all SMI-A users that are not explicitly mapped in the User Mapping section.

If a default mapping is not provided, then all unmapped SMI-A users inherit the same access as the account used to connect to the switch.

Only one default mapping scheme is allowed for each fabric.

1.Launch the Brocade SMI Agent Configuration Tool.

2.Click Default User Mapping in the menu tree (see Figure 8).

FIGURE 8 Default user mapping

3.Click the Stop Server to stop the SMI-A, if it is running. This button is unavailable if the server is already stopped.

4.Click Add.

5.Fill out the Default User Mapping Configuration dialog box and click OK.

The Proxy IP field is optional. If you do not specify the IP address of the proxy switch, then all unmapped SMI-A users can access the fabric with the same RBAC role as the given switch user name.

The SMIA SwitchUser field is mandatory.

The Default User Password field is mandatory if Radius Server Authentication is enabled; otherwise, it is optional. If you enter a password, it must be valid, even if it is optional.

20

Brocade SMI Agent User’s Guide

 

53-1001778-01

Image 36
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 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