The LDAP script needs to be configured with the details of your LDAP installation, has this been done? Properties you need to set are:
Location of the LDAP servers
Base DN to search from
A username/password to use to bind to LDAP to look up account details
The groups in your AD environment that should have access to Smarts (@LDAPGROUPS and @LDAPADMINGROUPS)
Exceptions for any local user accounts you want to bypass LDAP (including admin accounts such as admin, BrokerPing, BrokerNonsecure, etc.)
You can also try setting the $LOGLEVEL to 9 and see if there are any errors returned. You can also use a utility like ldapread to make sure your LDAP settings work beforehand.
Just confirming the format of your environment, can you please make sure the full path name is used e.g. SM_AUTHORITY="IDENTIFY=sm_authority, AUTHENTICATE=/usr/bin/perl /opt/InCharge/SAM/smarts/local/conf/sm_authority.pl" (You have a spelling mistake in your entry above, SM_AUTHORUTY should have an I not a U)
The sso.conf file is only used if you also have Watch4net 6.2 and are using the Companion UI virtual appliance to integrate the two products so that you can see the Smarts dashboards etc. from within Watch4net. Is this what you are trying to do?
If you are just trying to get LDAP/AD authentication to work with Smarts, it depends on the OS of the machine you have installed Smarts on.
If installed on a Windows machine, you can just add the users as username@domain (This is the long name of your domain e.g. company.local) to SAM in the Global Administration console, and then in your serverConnect.conf file add the users as follows:
*:username@domain: :All
And then they should be able to login using their domain accounts.
If you have installed Smarts on Linux, it is possible to get LDAP/AD authentication working, however you will need to have a custom SM_AUTHORITY and script set and I don't believe this is generally available. You may wish to contact EMC support to see if they will supply the script.
Are you trying to use LDAP for smarts authentication or setting up watch4net , cui and smarts integration with SSO?
If the former, check the sm_authority script to see if the script points to correct smarts install directory. if still not working, make sure ldap connectivity is present to the server you have smarts on. if still not working, contact emc support .
if latter, the documentation provided earlier should be sufficient enough to set up ss0 for watch4net and smarts.
I inherited an old installation of EMC smarts which already has the sm_authority file . But LDAP authentication is not enabled. We are not using watch4net and the authentication is only for the console. We running smarts on a Linux servers (multiple servers). Can somebody help me with some pointers as to what needs to be done.
BenimusIQ
12 Posts
4265
0
Posted June 4th, 2013 16:00
Hi James,
The LDAP script needs to be configured with the details of your LDAP installation, has this been done? Properties you need to set are:
You can also try setting the $LOGLEVEL to 9 and see if there are any errors returned. You can also use a utility like ldapread to make sure your LDAP settings work beforehand.
Just confirming the format of your environment, can you please make sure the full path name is used e.g. SM_AUTHORITY="IDENTIFY=sm_authority, AUTHENTICATE=/usr/bin/perl /opt/InCharge/SAM/smarts/local/conf/sm_authority.pl" (You have a spelling mistake in your entry above, SM_AUTHORUTY should have an I not a U)
Benjamin Johns
Senior Technology Consultant
iQ Consult Pty Ltd