Hi Georg,
this is possible but you would need to use 2 separate VCS-C's to do this, where 1 VCS-C is joined to the AD domain and configured to do NTLM authentication for Movi/Jabber Video provisioning requests, and where the other VCS-C is configured to use local database/LDAP authentication for Movi/Jabber Video provisioning requests.
Further, you would have to create two separate folders in TMS Provisioning Directory, where one folder houses the AD users and the other folder houses the non-AD users.
Lastly, you would have to configure the Internal Server setting on the Movi/Jabber Video so that the AD users get their provisioning configuration from the VCS-C which is configured for NTLM, while the non-AD users get their provisioning configuration for the non-NTLM VCS-C.
Now if you bring a VCS-E into the mix, so that both AD and non-AD users will also be logging in via the VCS-E, this will get a lot more complicated, since you would somehow have to ensure that a provisioning request from an AD user gets proxied through to the NTLM-enabled VCS-C while provisioning requests from non-AD users get proxied through to the non-NTLM VCS-C. This could be done with clever search rules, but that requires that you have an URI scheme for your provisioning users which allows you to determine if a provisioning request originates from an AD-based user or not.
In summary, this can be done, but it adds significant administrative overhead and would probably complicate troubleshooting quite a bit if that is ever required, and I would strongly suggest that you instead try to get all of the provisioning users into AD if possible.
Regards
Andreas
