- What is the BlackBerry AtHoc User Sync Client?
- User synchronization process overview
- Install and set up the BlackBerry AtHoc User Sync Client
- Execute the BlackBerry AtHoc User Sync Client
- Configure the data integration file
- Configuration overview
- Data adapter configuration
- Data processor configuration
- Data synchronizer configuration
- Synchronize LDAP groups
- How to synchronize users for enterprise user moves
- How to bulk update users' physical location
- How to configure organization subscription with the User Sync Client and API
- Troubleshoot the User Sync Client
- Appendix A: Adtools.exe
- Appendix B: Migrate from LDAP Sync Client version 1.2.7 to BlackBerry AtHoc User Sync Client
- Appendix C: Differences between the CSV Importer Tool and the BlackBerry AtHoc User Sync Client
- BlackBerry AtHoc Customer Support Portal
- Documentation feedback
Field descriptions
- <orgCode>: The organization code that you set up in theBlackBerry AtHocmanagement system in the General Settings.
- <url>: The URL of theBlackBerry AtHocserver.
- <username>: TheBlackBerry AtHocusername used to send web API requests.
- <isEncrypted>: If the password is encrypted, its value is "true", otherwise it is "false". The default is “false.”
- <password>: TheBlackBerry AtHocpassword used to send web API requests.
- <syncSource>: Required for static list synchronization. The synchronization source must be predefined in theBlackBerry AtHocsystem.
- <clientId>: Unique identifier for your LDAPSync client after the provisioning step.
- <clientSecret>: OAuth2 client secret that is returned after you provision the LDAP Sync client. Do not share this secret.
- <clientCertificate>: (Optional) This node is required if you want to append certificates in data sync requests. This node has following sub nodes:
- <subject>: (Optional) Subject of the specific certificate that you want to use.
- <storeName>: (Optional) The name of the certificate store.