If not, the user is created on inSync Cloud and the user device is activated. If the user exists on inSync Cloud, the device is activated. The inSync Client sends the user details and the mass deployment token to inSync Cloud for verification. inSync Cloud communicates with the AD/LDAP Server through inSync Connector to query the user details. When activating inSync Client during the mass deployment process: At the end of the inSync Client mass deployment process, the users log on to their computer using their AD/LDAP credentials.If inSync Cloud is configured to fetch user details periodically, it sends its query to the inSync Connector once every 24 hours.įor more information, see Adding a group of users by importing details from an Active Directory. The communication is facilitated by the inSync Connector. When importing user details: When you are creating users by importing their details from the AD/LDAP Server, inSync Cloud fetches the user details from the AD/LDAP Server.The inSync Connector facilitates communication.įor more information, see Creating an AD/LDAP Mapping. When creating AD/LDAP Mapping, inSync Cloud queries the AD/LDAP server to retrieve the name of the Base DN, Organizational Units, and Groups. During AD/LDAP Mapping creation: You must create AD/LDAP Mapping if you want to create inSync users by importing their details from the AD/LDAP Server.The following points outline some of the use cases for the inSync Connector. The inSync Connector connects with the AD/LDAP Server only when required. This means that you do not need to ensure high availability (HA) for the inSync Connector. Backups and restores from user devices on which inSync Client is activated will work as usual even if the computer where you installed the inSync Connector is not available. InSync uses the inSync Connector only while authenticating and activating inSync Client deployed on user devices.
InSync Connector role in AD/LDAP Environment
0 kommentar(er)
