Bug #10067
closed
If an LDAP attribute is missing the related LDAP errors are not reported in UI (silent fail)
Added by François ARMAND about 7 years ago.
Updated over 4 years ago.
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Very Small
Description
The reported error is:
[2017-01-24 16:53:01] ERROR com.normation.ldap.sdk.RwLDAPConnection - Exception ignored (by configuration) when trying to modify entry 'directiveId=61d6bce5-116c-4e0b-85bf-93bdecc3eef5,activeTechniqueId=ab90f00a-d206-42dd-aa1b-9b493f2b4932,techniqueCategoryId=applications,techniqueCategoryId=Active Techniques,ou=Rudder,cn=rudder-configuration'. Reported exception was: serializedTags: attribute type undefined
com.unboundid.ldap.sdk.LDAPException: serializedTags: attribute type undefined
at com.unboundid.ldap.sdk.LDAPConnection.modify(LDAPConnection.java:2513) ~[unboundid-ldapsdk-2.3.6.jar:2.3.6]
at com.normation.ldap.sdk.RwLDAPConnection$$anonfun$10$$anonfun$apply$7.apply(LDAPConnection.scala:541) ~[scala-ldap-4.1.0~beta2-SNAPSHOT.jar:na]
at com.normation.ldap.sdk.RwLDAPConnection$$anonfun$10$$anonfun$apply$7.apply(LDAPConnection.scala:541) ~[scala-ldap-4.1.0~beta2-SNAPSHOT.jar:na]
at scala.util.control.Exception$Catch.apply(Exception.scala:103) ~[na:na]
....
That error certainly should not be ignored.
It may happen since the start of (Rudder) times.
- Subject changed from If LDAP attribute is missing, related LDAP error are not reported in UI (silent failt to If LDAP attribute is missing, related LDAP error are not reported in UI (silent fail)
- Description updated (diff)
- Category set to Web - UI & UX
- Severity set to Major - prevents use of part of Rudder | no simple workaround
- User visibility set to Infrequent - complex configurations | third party integrations
- Priority changed from 25 to 24
- Priority changed from 24 to 38
- Priority changed from 38 to 36
- Assignee set to François ARMAND
- Priority changed from 36 to 34
- Effort required set to Very Small
- Priority changed from 34 to 58
- Target version set to 5.0.15
- Status changed from New to In progress
This one is only reported with OpenLDAP, not with the test server in unboundID SDK.
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/2583
OK, actually I'm not sure why we ignore most of the case set to be ignored by default here:
NO_SUCH_ATTRIBUTE => it's clearly a failure in all case, we are adding something not in the schem
UNDEFINED_ATTRIBUTE_TYPE => same
INVALID_ATTRIBUTE_SYNTAX => we are trying to add for ex a bool to a string, clearly an error.
INVALID_DN_SYNTAX => clearly an error we want to catch
ENCODING_ERROR => same.
Perhaps keep that one:
ATTRIBUTE_OR_VALUE_EXISTS, ENTRY_ALREADY_EXISTS => for idempotency
- Status changed from Pending technical review to Pending release
- Subject changed from If LDAP attribute is missing, related LDAP error are not reported in UI (silent fail) to If an LDAP attribute is missing the related LDAP errors are not reported in UI (silent fail)
- Name check changed from To do to Reviewed
- Fix check changed from To do to Checked
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0.15 which was released today.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by