Setauthparam -f ldap-server 10.10.10.10 setauthparam -f ldap-server-hn setauthparam -f kerberos-realm MYDOMAIN.COM setauthparam -f binding sasl setauthparam -f sasl-mechanism GSSAPI setauthparam -f accounts-dn “OU=Users,DC=mydomain,DC=com” setauthparam -f account-obj user setauthparam -f account-name-attr sAMAccountName setauthparam -f memberof-attr memberOf setauthparam -f super-map "CN=3ParAdministrators,OU=groups,DC=mydomain,DC=com" setauthparam -f browse-map "CN=3ParRead,OU=groups,DC=mydomain,DC=com" Check Configuration Make sure your kerberos-realm matches AD (its case sensitive) Setauthparam -f -clearall
#Hpe 3par ssmc login error windows
The parts in bold are what you will need to change, everything else should remain the same in a standard Windows environment.
![hpe 3par ssmc login error hpe 3par ssmc login error](http://4.bp.blogspot.com/-WKgLpyLIDjo/VVN9--tV-wI/AAAAAAAAANY/lcTzTOEw85k/s1600/SSMC_detail_admin_first.png)
#Hpe 3par ssmc login error code
As always please use at your own risk and note the first line of code clears out your current authentication configuration.
![hpe 3par ssmc login error hpe 3par ssmc login error](https://media.zones.com/images/products/D931F820-AE33-43D2-AFF7-DFD700B72B2F.jpg)
![hpe 3par ssmc login error hpe 3par ssmc login error](https://1.bp.blogspot.com/-byB8KdLHw3c/Xt85bOhyTiI/AAAAAAAAGMY/uyJ5niV6iLQLIax076J68sms2gtcCw7BQCLcBGAsYHQ/s1600/01_3par_error.png)
![hpe 3par ssmc login error hpe 3par ssmc login error](https://www.vbrainstorm.com/wp-content/uploads/2015/04/AllowLogonLocally.png)
Rather than logging onto your 3PAR with local user accounts you can use AD to authenticate users and determine what rights they have within the system.