Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

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

Last Updated: 3/22/2024Categories: TroubleshootingTotal Views: 3182Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

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.

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.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - SMARTS

Take Our Survey

Support Assistant