Translate local exceptions from your endpoint system Java API into exceptions provided by the LDAP protocol with the closest possible ResultCodeEnum values.
Finding a perfect match between errors encountered in implementing a custom connector and appropriate classes extending LdapException and ResultCodeEnum values is not always possible. However, it is worth giving it, and the messages chosen for exceptions, careful thought. Keep in mind that these choices directly affect the content of the Provisioning Server’s log messages, and are therefore important when troubleshooting.
When raising exceptions in your connector code (possibly by translating native endpoint exceptions), use your connectors ldapExceptionPrefix as the start of all exception messages. Using this prefix distinguishes them from exceptions originating from the ApacheDS/CA IAM CS framework levels of the software stack.
Note: For more information, see the SDK sample connector for examples.
|
Copyright © 2013 CA.
All rights reserved.
|
|