Unable to authenticate test user username This is a change from iLO 4 where the presence of the OData-Version header caused iLO 4 to remove pre-Redfish properties from GET responses. Unlike iLO 4, the service does not behave differently based upon the presence or absence of the OData-Version header. Initiating Directory Settings diagnostic for server ĭirectory Server address resolved to 192.168.132.30Īccepting Directory Server certificate for /CN= signed by /DC=lcl/DC=domain/CN=server2 iLO 5 assumes all requests are to Redfish REST resources are Redfish requests. When I perform a "test settings", the failure occurs at "User Authentication" with the following log.
#HP ILO 4 USE DIRECTORY DEFAULT SCHEMA LICENSE#
Our iLO2 card has the Advanced license and is running v. To access the Web GUI for iLO, type the DNS name or IP address in the browser URL.
#HP ILO 4 USE DIRECTORY DEFAULT SCHEMA SOFTWARE#
For the web interface to be accessible, the iLO software version should be 1.80 and later. We have 4 AD users (all Domain Admins) in the iLO group which we wish to give access to the iLO2. This is a schema-free integration using the iLO Web Interface. "Directory User Context 2: OU=Users,DC=domain,DC=lclįor User Admin - Group Accounts, the "Administrator" group is set with a "Security Group Distinguished Name" of CN=iLO,CN=Users,DC=domain,DC=lcl. I am using the Default Directory Schema with Kerberos Authentication disabled and Local User Account Enabled and am using LDAP Port 636.
I've configured my iLO for active directory integration both manually and using HPQLOMIG.exe.
Using Directory Default Schema, "Directory Server Address" is "", LDAP Port is 636, "Directory User Context 1": CN=Users,DC=domain,DC=lcl Current config is on a D元60p G8 with the latest iLO firmware (v. I have used the "Lights-Out Migration Utility" to do a config, have done several myself (based on the "Conveniently integrating HP ProLiant Lights-Out processors with Microsoft® Active Directory" Integration Note, and nothing is working. I have been trying for several days to get a new iLO2 card to play nicely with Active Directory. 4) To access the Web GUI for iLO, type the DNS name or IP address in the browser URL. 3) For the web interface to be accessible, the iLO software version should be 1.80 and later. Something that has been on my list for a while to to add SSL certificates to all the various internal apps and management web interfaces so I am not just clicking through the certificate warning in the browser.
0 kommentar(er)
