Last updated on JULY 04, 2012
Applies to:Oracle Communications ASAP Cartridges - Version 1.0.0 to 1.0.0 [Release 1.0.0]
Information in this document applies to any platform.
The ASAP MasterLDAP Cartridge does not support Modify-Delete commands.
The cartridge appears to be hard coded to use Modify-Replace commands, as opposed to Modify-Delete when removing an LDAP attribute. This is causing an issue for the system triggers that are based on specific operation types i.e. Modify-Delete.
When using the cartridge, if a null or a space is entered for a given LDAP attribute, the cartridge results in sending down a Modify-Replace request to the LDAP server (DirContext.modifyAttributes(DN, 2, attrs);). In the production environment however, the MasterLDAP operation is based upon LDAP triggers, e.g. when a Modify-Delete is run against the shapingTemplate attribute under the ADSL object, the trigger runs against that event and stops the subscribers service being shaped, where, as when they recieve a Modify-Replace, the trigger assumes that a new shaping profile is being configured, not removed, thus results in an invalid shaping template and a broken ASDL service.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms