Smarts SAM: Setting up SSO in Watch4net doesn't propagate the user information to Smarts.
Article ID: 332221
Updated On:
Products
VMware Smart Assurance
Issue/Introduction
Symptoms:
We are running SMARTS, W4N and SSO betwen each product.
In SMARTS, we have only added people in the Global Console and added them in the correct group. No mention in the serverconnect.conf.
In W4N, they are correctly added. Certains Users can connect to Watch4net and see data in Watch4net from SMARTS (topology map, browse, notifications, ...).
Others users get a 403 error indicating that they need to login but do not receive any message or popup.
However, they cannot connect to SMARTS itself using webconsole or Smarts Global Console, they get a login failed.
We are running SMARTS, W4N and SSO betwen each product.
In SMARTS, we have only added people in the Global Console and added them in the correct group. No mention in the serverconnect.conf.
In W4N, they are correctly added. Certains Users can connect to Watch4net and see data in Watch4net from SMARTS (topology map, browse, notifications, ...).
Others users get a 403 error indicating that they need to login but do not receive any message or popup.
However, they cannot connect to SMARTS itself using webconsole or Smarts Global Console, they get a login failed.
Environment
VMware Smart Assurance - SMARTS
Resolution
Changing the password in M&R for a particular user will not change it in Smarts. This has to be done manually.
An enhancement request has been submitted for a complete SSO feature within SA Suite.
For more details or for a status on this enhancement, please open a ticket with support.
An enhancement request has been submitted for a complete SSO feature within SA Suite.
For more details or for a status on this enhancement, please open a ticket with support.
Feedback
Yes
No
Powered by
