Table of Contents
Atea Anywhere LDAP Sync
Atea Anywhere LDAP Sync enables customers to automatically sync and manage personal VMR in Atea Anywhere
The Service can be installed at the customer site on any Windows machine with access to both the LDAP Catalog and Internet.
Based on .NET Framework 4.6.1 and has no special hardware requirements.
Normal LDAP Read rights are sufficient for this service.
Supported LDAP System
-
Active Directory (AD)
-
Azure Active Directory
-
OpenLDAP
-
Novell eDirectory
-
Oracle Internet Directory
- CSV File
LDAP Settings
| Field | Description | Example |
| Username | LDAP Server Username | user@example.com | cn=user,ou=Sales,ou=East,dc=example,dc=com |
| Password | LDAP Server Password | |
| Server | LDAP Server | Domain name, fqdn or IP Address |
| Path |
Use the distinguishedName path for where to start searching in LDAP |
ou=Sales,ou=East,dc=example,dc=com |
| Member ACL | To import users that belong to a specific group, you can filter on the memberOf AD attribute. For example, to only import users who are members of the cn=sales,ou=groups,dc=example,dc=com group, you would set the LDAP user filter on your template to: | cn=sales,ou=groups,dc=example,dc=com |
| Host PIN Attribute |
Optionaly you can spesify a LDAP Attribute with are holding the user Host PIN for the VMR. Leve blank to autogenetate PIN Codes |
extensionAttribute11 |
| Guest PIN Attribute |
Optionaly you can spesify a LDAP Attribute with are holding the user Guest PIN for the VMR. Leve blank to autogenetate PIN Codes |
extensionAttribute12 |
| Mail Domains | A comma separated list of domain for the LDAP mail Attribute | example1.com,example2.com |
Atea Anywhere Settings
| Field | Description | Example |
| Username | Atea Anywhere API Username | user@anywhere.vc |
| Password | Atea Anywhere API Password | |
| VMR Template | Template name defined by Atea. | |
| VMR Name | Template for creating the VMR Name |
{{givenName}} {{sn}} |
| VMR Alias | Template for creating the VMR Alias |
meet.{{mailPrefix}}@anywhere.vc meet.{{mailPrefix}}@{{mailSuffix}} meet.{{mailPrefix}}@example.{{mailSuffix}} meet.{{mai}} meet.{{givenName}}.{{sn}}@anywhere.vc |
| VMR Description | Template for creating the VMR Description |
{{givenName}} {{sn}} |
| VMR Pin Lenght |
Lenght when automatcly creating PIN codes. PIN codes can be from 4-20 digits |
4 |
Valid replacement patterns
- {{sn}}
- {{givenName}}
- {{mail}}
- {{mailPrefix}}
- {{mailSuffix}}
- {{sAMAccountName}}
- {{telephoneNumber}}
- {{mobile}}
- {{displayName}}
- {{ipPhone}}
Windows Service Settings
| Description | Example | |
| Sync every | Set the sync interval | 4 hours |
| Log Level | Set the Service log level. | Info |
| Proxy |
Use proxy server when connecting to Atea Anywhere. Service connect to https://admin.anywhere.vc:443
|
http://fqdn:8080 |
FAQ:
Q:
Can users change their pincodes on the adminportal after it has been synced from AD ?
A:
Yes, pincodes can be changed and won't be overwritten again nex time a sync happens