[asterisk-bugs] [Asterisk 0018478]: [patch] Ldap Can't modify unknown attribute

[Asterisk Bug Tracker]

The following issue has been CLOSED 
====================================================================== 
https://issues.asterisk.org/view.php?id=18478 
====================================================================== 
Reported By:                moos3
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18478
Category:                   Resources/res_config_ldap
Reproducibility:            always
Severity:                   tweak
Priority:                   normal
Status:                     closed
Asterisk Version:           1.6.2.14 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.2 
SVN Revision (number only!): 288822 
Request Review:              
Resolution:                 open
Fixed in Version:           
====================================================================== 
Date Submitted:             2010-12-15 12:10 CST
Last Modified:              2011-01-30 09:13 CST
====================================================================== 
Summary:                    [patch] Ldap Can't modify unknown attribute
Description: 
With a ldap as the realtime source it will when it can't modify anything it
returns:
res_config_ldap.c:1317 update_ldap: Couldn't modify
dn:uid=rgenthner,ou=People,dc=example,dc=com because Undefined attribute
type

Which doesn't give you any insight on what attribute its trying to modify
====================================================================== 

---------------------------------------------------------------------- 
 (0131241) seanbright (manager) - 2011-01-30 09:13
 https://issues.asterisk.org/view.php?id=18478#c131241 
---------------------------------------------------------------------- 
There is already a large section of debug output in this section, you just
need to turn on debug logging to see it:

<pre>
*CLI> core set debug 5</pre>
And make sure that debug logging is enabled somewhere in your logger.conf
file. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-01-30 09:13 seanbright     Note Added: 0131241                          
2011-01-30 09:13 seanbright     Status                   needs license => closed
======================================================================