HP Xw460c HP Integrated Lights-Out 2 User Guide for Firmware 1.75 and 1.77 - Page 50

Using two-factor authentication with directory authenticatio, is CN=John Doe, OU=IT, DC=MyCompany

Page 50 highlights

After you have selected a certificate, if the certificate is protected with a password or if the certificate is stored on a smart card, a second page appears prompting you to enter the PIN or password associated with the chosen certificate. The certificate is examined by iLO 2 to ensure it was issued by a trusted CA by checking the signature against the CA certificate configured in iLO 2. iLO 2 determines if the certificate has been revoked and if it maps to a user in the iLO 2 local user database. If all of these tests pass, then the normal iLO 2 user interface appears. If your credential authentication fails, the Login Failed page appears. If login fails, you are instructed to close the browser, open a new browser page, and try connecting again. If directory authentication is enabled, and local user authentication fails, iLO 2 displays a login page with the directory user name field populated with either the User Principal Name from the certificate or the Distinguished Name (derived from the subject of the certificate). iLO 2 requests the password for the account. After providing the password, you are authenticated. Using two-factor authentication with directory authentication In some cases, configuring two-factor authentication with directory authentication is complicated. iLO 2 can use HP Extended schema or Default Directory schema to integrate with directory services. To ensure security when two-factor authentication is enforced, iLO 2 uses an attribute from the client certificate as the directory user's login name. Which client certificate attribute iLO 2 uses is determined by the Certificate Owner Field configuration setting on the Two-Factor Authentication Settings page. If Certificate Owner Field is set to SAN, iLO 2 obtains the directory user's login name from the UPN attribute of the SAN. If the Certificate Owner Field setting is set to Subject, iLO 2 obtains the directory user's distinguished name from the subject of the certificate. Which Certificate Owner Field setting to choose depends on the directory integration method used, the directory architecture, and what information is contained in the user certificates that are issued. The following examples assume you have the appropriate permissions. Authentication using Default Directory Schema, part 1: The distinguished name for a user in the directory is CN=John Doe,OU=IT,DC=MyCompany,DC=com, and the following are the attributes of John Doe's certificate: • Subject: DC=com/DC=MyCompany/OU=IT/CN=John Doe • SAN/UPN: [email protected] Authenticating to iLO 2 with username:[email protected] and password, will work if two-factor authentication is not enforced. After two-factor authentication is enforced, if SAN is selected on the TwoFactor Authentication Settings page, the login page automatically populates the Directory User field with [email protected]. The password can be entered, but the user will not be authenticated. The user is not authenticated because [email protected], which was obtained from the certificate, is not the distinguished name for the user in the directory. In this case, you must select Subject on the TwoFactor Authentication Settings page. Then the Directory User field on the login page will be populated Configuring iLO 2 50

  • 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
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235

Configuring iLO 2 50
After you have selected a certificate, if the certificate is protected with a password or if the certificate is
stored on a smart card, a second page appears prompting you to enter the PIN or password associated
with the chosen certificate.
The certificate is examined by iLO 2 to ensure it was issued by a trusted CA by checking the signature
against the CA certificate configured in iLO 2. iLO 2 determines if the certificate has been revoked and if
it maps to a user in the iLO 2 local user database. If all of these tests pass, then the normal iLO 2 user
interface appears.
If your credential authentication fails, the Login Failed page appears. If login fails, you are instructed to
close the browser, open a new browser page, and try connecting again. If directory authentication is
enabled, and local user authentication fails, iLO 2 displays a login page with the directory user name
field populated with either the User Principal Name from the certificate or the Distinguished Name
(derived from the subject of the certificate). iLO 2 requests the password for the account. After providing
the password, you are authenticated.
Using two-factor authentication with directory authentication
In some cases, configuring two-factor authentication with directory authentication is complicated. iLO 2
can use HP Extended schema or Default Directory schema to integrate with directory services. To ensure
security when two-factor authentication is enforced, iLO 2 uses an attribute from the client certificate as
the directory user's login name. Which client certificate attribute iLO 2 uses is determined by the
Certificate Owner Field configuration setting on the Two-Factor Authentication Settings page. If Certificate
Owner Field is set to SAN, iLO 2 obtains the directory user's login name from the UPN attribute of the
SAN. If the Certificate Owner Field setting is set to Subject, iLO 2 obtains the directory user's
distinguished name from the subject of the certificate.
Which Certificate Owner Field setting to choose depends on the directory integration method used, the
directory architecture, and what information is contained in the user certificates that are issued. The
following examples assume you have the appropriate permissions.
Authentication using Default Directory Schema, part 1:
The distinguished name for a user in the directory
is CN=John Doe,OU=IT,DC=MyCompany,DC=com, and the following are the attributes of John Doe's
certificate:
Subject: DC=com/DC=MyCompany/OU=IT/CN=John Doe
Authenticating to iLO 2 with username:[email protected] and password, will work if two-factor
authentication is
not
enforced. After two-factor authentication is enforced, if SAN is selected on the Two-
Factor Authentication Settings page, the login page automatically populates the Directory User field with
[email protected]. The password can be entered, but the user will
not
be authenticated. The
user is not authenticated because [email protected], which was obtained from the certificate,
is not the distinguished name for the user in the directory. In this case, you must select
Subject
on the Two-
Factor Authentication Settings page. Then the Directory User field on the login page will be populated