"The eDirectory team are also suggested we could switch in the a Novell API solution? Has anyone done something along these lines with Remedy (instead of using the supplied AREA/ARDBC plugins)?"
You could write your own AREA plugin that uses the Novell API for all directory calls. This would probably be the best route to accomplish all the things your Novell people are asking, if you or they have the skills to write the plugin. The AREA plugins are written in C, so you would need to use the Novell C api to write the plugin. Just keep in mind that the area plugin is a interface that implements a specific set of calls, you can do whatever you want within these calls (increment counter x, perform the authentication using api z, etc.). Axton Grams On 4/10/07, Kevin Murray <[EMAIL PROTECTED]> wrote:
Hi All, Environment: ARSystem 6.3 Patch 20, HPUX 11i, Oracle 9i currently using ARSystem authentication We are planning to implement the LDAP plugins (both AREA and ARDBC) to connect to the corporate Novell eDirectory (Recent Version - tbc), running on separate hardware. Our eDirectory team are keen to understand the logic behind the supplied plug-ins i.e what specific function calls, does it use when interacting with eDirectory, and what attributes does it interact with? I'm specifically interested in the AREA plugin, the ARDBC is very much specific to what you include in the vendor form? e.g. Does the plugin increment the Bad Password counter attribute? In my experience No, this is managed centrally by LDAP Does the plugin update the last logged on attribute? In my experience no, this is managed centrally by LDAP Does the plugin implement password history? Don't know, but don't think it's really relevant as the password is not set through Remedy managed centrally again through eDirectory Does the plugin update the loginGraceLimit? Don't know Does the plugin update the loginGraceRemaining? Don't know Setting-up the integration should be OK, completed it before elsewhere however never had anyone ask me the above before. I don't think providing them with the remedy manual/knowledge base material will work. The documentation provided in the guides/knowledge base are all very ARSystem centric. The eDirectory team are also suggested we could switch in the a Novell API solution? Has anyone done something along these lines with Remedy (instead of using the supplied AREA/ARDBC plugins)? Any information appreciated. Kind Regards, Kevin ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
