HP 3PAR StoreServ 7400 2-node HP 3PAR Command Line Interface Administrator& - Page 29

Configuring Binding Parameters, Configuring the CA Certificate, Step 1, Configuring

Page 29 highlights

3. Set the LDAP server's host name by issuing the setauthparam ldap-server-hn command, where is the value displayed by either using the ldapsearch command or ldp.exe in Step 1. NOTE: The value displayed for the defaultNamingContext is used later in "Configuring Account Location Parameters" (page 24). Example: % ldapsearch -LLL -x -H ldap://192.168.10.13 -b "" -s base dnsHostName ldapServiceName defaultNamingContext dn: dnsHostName: domaincontroller.3par.com ldapServiceName: 3par.com:[email protected] defaultNamingContext: DC=3par,DC=com The example above corresponds to Step 1 and displays the following: • The LDAP server's IP address is 192.168.10.13. • The DNS_HostName is domaincontroller.3par.com. • The defaultNamingContext is DC=3par,DC=com. system1 cli% setauthparam -f ldap-server 192.168.10.13 system1 cli% setauthparam -f ldap-server-hn domaincontroller.3par.com The example above corresponds to Step 2 through Step 3. Configuring Binding Parameters After you have configured the connection parameters to your LDAP server, you must configure the binding (authentication) parameters for users. 1. Issue the setauthparam binding simple command. Example: system1 cli% setauthparam -f binding simple 2. Issue the setauthparam user-atter command to set the attribute used to form a DN to the Windows domain. Example setauthparam -f user-attr NTDOM1\\ In the example above, the Windows domain is NTDOM1. Configuring the CA Certificate To configure the CA certificate: 1. Obtain the location of the CA certificate from the Active Directory server's administrator. NOTE: If the certificate ends in the file extension .crt, it will need to be converted to a form compatible with the setauthparam command. 2. If necessary, convert the certificate to .cer file format. On a Windows system: a. Double-click the certificate. Configuring LDAP Connections 29

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204

3.
Set the LDAP server’s host name by issuing the
setauthparam ldap-server-hn
<DNS_HostName>
command, where
<DNS_HostName>
is the value displayed by either
using the
ldapsearch
command or
ldp.exe
in
Step 1
.
NOTE:
The value displayed for the defaultNamingContext is used later in
“Configuring
Account Location Parameters” (page 24)
.
Example
:
% ldapsearch -LLL -x -H ldap://192.168.10.13 -b "" -s base dnsHostName
ldapServiceName defaultNamingContext
dn:
dnsHostName: domaincontroller.3par.com
ldapServiceName: 3par.com:[email protected]
defaultNamingContext: DC=3par,DC=com
The example above corresponds to
Step 1
and displays the following:
The LDAP server’s IP address is
192.168.10.13
.
The
DNS_HostName
is
domaincontroller.3par.com
.
The
defaultNamingContext
is
DC=3par,DC=com
.
system1 cli% setauthparam -f ldap-server 192.168.10.13
system1 cli% setauthparam -f ldap-server-hn domaincontroller.3par.com
The example above corresponds to
Step 2
through
Step 3
.
Configuring Binding Parameters
After you have configured the connection parameters to your LDAP server, you must configure the
binding (authentication) parameters for users.
1.
Issue the
setauthparam binding simple
command.
Example
:
system1 cli% setauthparam -f binding simple
2.
Issue the
setauthparam user-atter <DN_attribute>
command to set the attribute
used to form a DN to the Windows domain.
Example
setauthparam -f user-attr NTDOM1\\
In the example above, the Windows domain is
NTDOM1
.
Configuring the CA Certificate
To configure the CA certificate:
1.
Obtain the location of the CA certificate from the Active Directory server’s administrator.
NOTE:
If the certificate ends in the file extension
.crt
, it will need to be converted to a
form compatible with the
setauthparam
command.
2.
If necessary, convert the certificate to
.cer
file format. On a Windows system:
a.
Double-click the certificate.
Configuring LDAP Connections
29