LDAP Sync does not consider two RTC End-User License Types
We are trying to figure out how to setup our LDAP auto groups and the LDAP Nightly Sync such that an automatic mapping of imported users to correct license type occurs (Contributor vs. Developer) based on LDAP auto group membership. However it seems this is currently not possible for two reasons (see below) and therefore we are being forced to manually update imported user profiles and reassign license types. Given that there are two distinct end-user license types (Contributor and Developer) the current recommended setup seems counterintuitive and defeats the purpose of having an automated LDAP sync process.
1). The documentation recommends creating only one LDAP auto group for end-users which maps to the internal JazzUsers group. We believe two internal groups would be more appropriate, say JazzContributors and JazzDevelopers. Then two LDAP auto groups could be setup to map to each.
2). The RTC product currently offers only one default license type mapping (Set Default Client Access License Key). We believe the product should allow for two such mappings - one for each license type.
We were wondering if this has already been considered, and if so, when such an enhancement might be made available. Or perhaps we are missing something? Please let us know your thoughts.
1). The documentation recommends creating only one LDAP auto group for end-users which maps to the internal JazzUsers group. We believe two internal groups would be more appropriate, say JazzContributors and JazzDevelopers. Then two LDAP auto groups could be setup to map to each.
2). The RTC product currently offers only one default license type mapping (Set Default Client Access License Key). We believe the product should allow for two such mappings - one for each license type.
We were wondering if this has already been considered, and if so, when such an enhancement might be made available. Or perhaps we are missing something? Please let us know your thoughts.