#dominoforever | Product Ideas Portal

 

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

LDAP: Acquire email address from external LDAP during Namelookup

Please provide a way to leverage the initial access performed by Domino to fetch additional attributes during the user logon phase.

Wants to access some additional attributes like Email id from LDAP.

This requirement came up because user have several thousands of access per minute and the LDAP is remote to the Domino application.

When using @Namelookup especially in a Directory Assistance context federating external LDAP servers (e.g. using [Exhaustive] lookup-type) the third parameter (itemtoreturn)

should be able to return an arbitrary array of attributes.

@NameLookup( [ lookupType ] ; username; itemtoreturn )

In the syntax above, the "itemtoreturn" should include additional attributes like "departmentNumber":"employeeNumber":"telephoneNumber" and so on.

This will allow to leverage the Directory Assistance internal pooling mechanism without requiring to make additional LDAP calls at application level increasing execution speed and I/O.

  • Guest
  • Mar 17 2021
  • Needs clarification
  • Attach files
  • Guest commented
    21 Apr 05:20pm

    Customers often do not allow external LDAP entries to be imported into domino.

    Furthermore this is against the principal of Directories Federation for which DA has been used.

  • Admin
    Thomas Hampel commented
    21 Apr 11:43am

    Why not set up DirSync and create a person document automatically?

  • Guest commented
    22 Mar 02:00pm

    When using @Namelookup especially in a Directory Assistance context federating external LDAP servers (e.g. using [Exhaustive] lookup-type) the third parameter (itemtoreturn)

    should be able to return an arbitrary array of attributes.

    @NameLookup( [ lookupType ] ; username; itemtoreturn )


    In the syntax above, the "itemtoreturn" should include additional attributes like "departmentNumber":"employeeNumber":"telephoneNumber" and so on.


    This will allow to leverage the Directory Assistance internal pooling mechanism without requiring to make additional LDAP calls at application level increasing execution speed and I/O.