sure, you can import as much AD domains as you want.
Configure it in your Data connections and Data Import.
I don´t think there´s a problem.
Here I mean using external authentication from AD. I understand that we can import data from multiple AD, but if I use external AD as authentication method with multiple domains. How does LDSD know which domain it should use for authentication? Thanks.
i think in this case you have to enter the Domain you want.
Are you using SSO?
I think LDSD looks at how you're logged on to Windows and matches this to the 'Network Logins' portion of the user record in LD. So as long as the 'Network Logins' information is correct it should work.
I think that is how it works....we're just starting to look at authentication from two domains ourselves but the actual work isn't starting for a little while yet.
Could you please provide more details on what you need, are the domain trusted ?.
As these might help.
If you are trying to setup Server Authentication as per following link, then you would need a different frameworks / web applications for each domain.
Well I'm not sure if this works but seems it is possible to use two domains in the Service Desk.
Earlier we use one domain for our users to logon to the service desk, let us say ABC\Loginname and recently some of them were changed to other domain let's say BCD domain and all we did was, we have added one more network login with that new domain as BCD\Loginname for those respective users. And those users were having two network login id's in the portal now. In our case the user was first removed from ABC domain and added in the BCD domain, so we did not come across this.
Coming to your case, if that user is present in those two domains and if you add those two domains in the Network login's then he/she should be able to access the service desk with those two network login id's.
Let us know, if this works.