Skip Navigation
  1. BlackBerry Docs
  2. BlackBerry AtHoc
  3. 1.2
  4. User Sync Client
  5. Appendix B: Migrate from LDAP Sync Client version 1.2.7 to BlackBerry AtHoc User Sync Client
  6. Migrate from mid to login_id

Migrate from mid to login_id

Terms
  • mid
    • The mid was the primary key when synchronizing in previous versions.
    • Display name in
      BlackBerry AtHoc
      : Mapping ID
    • Common Name in
      BlackBerry AtHoc
      : mapping_id
  • login_id
    • The login_id is the Common Name for Username in
      BlackBerry AtHoc
      . It is the primary key when synchronizing against
      BlackBerry AtHoc
       with the User Sync Client.
    • Display name in
      BlackBerry AtHoc
      : Username
    • Common Name in
      BlackBerry AtHoc
      : login_id
What is changing?
In LDAP Sync Client 1.2.7 and lower, all user synchronization happened through older SDK code. The SDK payload accepted mid in the input payload field to look up and synchronize users. In the User Sync Client, the API requires login_id as the primary key.
Behavior prior to User Sync Client:
  • For the user payload, if a user did not exist with the provided mid, it would create a new user and set the mapping_id and the login_id to mid if the login_id was not separately provided in the payload. If mid was present in the payload, and if the user existed with the same mapping_id, it would then update that record for the user.
  • For the distribution list synchronization payload, all mappings were managed by looking up members by their mid.
Behavior in User Sync Client:
  • All user lookup and synchronization happens using the login_id (Username.)
  • All distribution list-to-user mappings are based on login_id.
  • The “mid” field is no longer supported.
Are you affected?
  1. Do you set a value for login_id in the template?
    1. Search for references to login_id.
    2. If you find any references, you have explicitly set a value for login_id.
    3. You need to use this LDAP attribute as the primary key. Whatever you previously set to mid can be set to mapping_id.
    4. Ensure that any LDAP attributes that you are using for login_id have memberExport=“true” in the
      AtHocDataIntegration.config
       file. Your configuration may have the setting for this attribute that was used for mid. Not making this update in the
      AtHocDataIntegration.config
       file will lead to errors during distribution list member synchronization.
  2. Does
    BlackBerry AtHoc
     have different values?
    1. Export all users to a .csv file. Include only the mid and username columns.
    2. Open the .csv file in Microsoft Excel.
    3. Add this formula to cell C1 and then fill down:
      =IF(A1<>B1,"No match","")
      .
    4. Filter to show only users who have No Match.
    5. Filter to show only users who have a mapping_id. This is not required when creating users in the UI.
    6. Any users left may be impacted if synced from the User Sync Client.
If you answered “No” to 1 and 2 above,
BlackBerry AtHoc
 automatically copies the mid to login_id. Switching them will not have an impact.
If you answered “Yes” to either 1 or two above, you will likely need to change the usernames of existing users. Contact
BlackBerry AtHoc
 customer support for assistance.