My Oracle Support Banner

LDAP Based Expire Rules For Messaging Server (Doc ID 2739556.1)

Last updated on DECEMBER 27, 2020

Applies to:

Oracle Communications Messaging Server - Version 8.1.0 and later
Information in this document applies to any platform.

Goal

Is there a way to have imexpire criteria defined on the user in LDAP?  Is there any way possible to accomplish this?

Currently, store.expirerule files are great, but doing something special on a per-user basis -- and multiply that by more than a hundred thousand users across 20 different backends -- would require getting involved in the provisioning process, which creates/updates the information in LDAP, and having that fire off something to the backends to create/update the store.expire rule files.

If an option existed on imexpire to look at an attribute on the user's LDAP entry, it could all be done with COS attributes on the users.

Anything that requires the provisioning system to interact with the backend would involve an ssh-type connection and something to create the files.
The security implications are a bigger problem than technically how to do it. And the coding effort to change the provisioning system is also non-trivial.
 

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.