Authenticating users without referring to the clientConnect.conf and serverConnect.conf files.
search cancel

Authenticating users without referring to the clientConnect.conf and serverConnect.conf files.

book

Article ID: 303748

calendar_today

Updated On:

Products

VMware Smart Assurance

Issue/Introduction

This article covers the steps for authenticating an user without referring to the clientConnect.conf and serverConnect.conf files.

Environment

Smarts 10.1.X

Resolution

You can create user accounts directly into the SAM repository.  However, passwords are not stored in the rps file, but are kept in the client and serverConnect.conf files.
Therefore, you cannot completely by-pass these files for authentication unless you have the following setup:

  1. The clientConnect.conf file has an entry in the User Access section as follows:
    *:*:<PROMPT>:<PROMPT>
  2. The serverConnect.conf file has the following entry at the bottom of the file:
    *:*:<SYS>:Monitor
  3. The username and password that you want to use should exist as an account on the OS that has SAM installed.

  4. Add the following line via dmctl:
    dmctl -s <SAM> create ICS_User::ICS-User-<usrname>
    Where <usrname> is the same user name as the one on the OS account in step 3 above.

  5. Start a SAM console and open the Global Manager Administration Console.  In the Users section, select the new user account and enable it via the GUI.