Smarts IP: How authentication details passed from SAM to Lower level APM domain

Products

• VMware Smart Assurance

Issue/Introduction

Symptoms:


Process of Passing the Authentication in serverConnect.conf and clientConnect.conf  between SAM and APM Domain.
How authentication details passed from SAM to Lower level APM domain


While using Browse Details of a Notification frmo Console it didn't ask for password.

Environment

VMware Smart Assurance - SMARTS

Cause

If the same user is configured in SAM and IP domain conf file with the different password for that particular user in IP domain   s Server and clientConnect.conf, It will prompt for you to provide your credentials.

Example 1 : In the below condition it won't ask for credentials.

C:\\InCharge8\\SAM\\smarts\\local\\conf

SAM   s conf file: User Name = test    Password = test

C:\\InCharge8\\IP\\smarts\\local\\conf

IP   s conf file: Username = test  Password = test

Example 2 : Credentials will be asked in the below case:

C:\\InCharge8\\SAM\\smarts\\local\\conf

SAM   s conf file:  User Name = test   Password = test

C:\\InCharge8\\IP\\smarts\\local\\conf

IP   s conf file:  Username = test  Password = test123

Resolution

Program Access is automatically (if user is logged into SAM as admin) taking the user in clientConnect.conf file in SAM ( default admin ) and doing a check in serverConnect.conf file in AMPM ( which also have default admin ) and if they match, there will not be any prompt.  Only if user in clientConnect.conf in SAM is not matching up with the user in serverConnect.conf file in AM, then a prompt will show. Also, it depends on what is the user you are using to login to SAM.  For example, if you are logged into SAM using 'test' ( or any user ), if this user is not in serverConnect.conf file in IP, then it will prompt for credentials. the key here is the user or *:*::<test> must be in serverConnect.conf file of AM. 

Basically, whichever user is logged into SAM, that user must have an entry in serverConnect.conf file in AM, If it does, then no prompt. The reason for the prompt is, first the program take the user that's already logged into SAM and try to do a match, if no match is found, then it will prompt and ask for the credential.