Actions
Bug #4922
closedRudder OpenLDAP Authentication sans ipv4 localhost
Status:
Released
Priority:
N/A
Assignee:
Category:
System integration
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
Rudder encounters issues when working with a server that has no ipv4 localhost assigned, attempting to connect to ldap results in errors unless "127.0.0.1" is specifically defined as the server the host (as opposed to localhost)
using localhost:
/opt/rudder/bin/ldapsearch -h localhost -p 389 -D "cn=manager,cn=rudder-configuration" -w 'ldap_password' -b 'cn=rudder-configuration' -s onelevel ldap_sasl_bind(SIMPLE): Can't contact LDAP server (-1)
using 127.0.0.1:
root@rudder:/# /opt/rudder/bin/ldapsearch -h 127.0.0.1 -p 389 -D "cn=manager,cn=rudder-configuration" -w 'ldap_password' -b 'cn=rudder-configuration' -s onelevel # extended LDIF # # LDAPv3 # base <cn=rudder-configuration> with scope oneLevel # filter: (objectclass=*) # requesting: ALL # # Nodes, rudder-configuration dn: ou=Nodes,cn=rudder-configuration objectClass: top objectClass: organizationalUnit ou: Nodes description: Branch that stores all the Nodes # Rudder, rudder-configuration dn: ou=Rudder,cn=rudder-configuration objectClass: top objectClass: organizationalUnit ou: Rudder description: Branch that stores all Rudder specific data # Inventories, rudder-configuration dn: ou=Inventories,cn=rudder-configuration objectClass: top objectClass: organizationalUnit ou: Inventories description: Inventory information # Application Properties, rudder-configuration dn: ou=Application Properties,cn=rudder-configuration ou: Application Properties objectClass: organizationalUnit objectClass: top # search result search: 2 result: 0 Success # numResponses: 5 # numEntries: 4
Actions