Skip to Main Content
HCL Connections Ideas Portal

Welcome to the HCL Connections Product Ideas Lab! 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 the 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, please visit our HCL Connections page.

Status No Plans to Implement
Categories 04. Profiles
Created by Guest
Created on May 10, 2019

The default value for PROF_IDHASH should better be 'e3b0c44298fc1c149afbf4c8996fb924'. Or allow null value for PROF_IDHASH.

PROF_IDHASH becomes "?" when registering new users who does not have email address. For users who does not have email address, PROF_IDHASH should be a fixed value 'e3b0c44298fc1c149afbf4c8996fb924'.

But if we register new user on LDAP and run sync_all_dns or populate_from_dn_file, the user's PROF_IDHASH is registered as "?". If a user already exists in PEOPLEDB, the PROF_IDHASH becomes to 'e3b0c44298fc1c149afbf4c8996fb924' once we re-run sync_all_dns or populate_from_dn_file. This seems a problem of initial registration.


We found the value of PROF_IDHASH is used for Verse integration. So it may no effect to use Connections. But the customer requires to have the same value for the initial registration. The TDI code should be updated or the default value for PROF_IDHASH should better be 'e3b0c44298fc1c149afbf4c8996fb924'. Or allow null value for PROF_IDHASH.

  • Attach files
  • Guest
    Jul 20, 2021

    The idhash is afaik used to have faster lookups from Verse, so having a not unique value makes absolutely no sense!