Configure both directories in exactly the same way (you can configure multiple Active Directories in QMC, e.g. for different domains in a forest). If users always visit your QlikView server from inside a Windows network, they will be recognized in any case (SSO), whether they are authrnticated in domain X, or Y, or Q or whatever you defined in QMC.
If users from your Yahoo domain visit from outside the company network, there is no previous authentication phase and they will be presented with a login page in any case (by Windows, or your web server or whatever service/tool you plan to use)
AD authentication doesn't travel well over the internet...
Thanks for your valuable inputs. Now my query on top of it is
As per my understanding in QV server there are two options
1) is default login
2) is through web form
but we can set up only one option at a time,
Case 1: In QV Server if we set default login page, then how to configure it for external user?
Case 2: In QV server if we setup web form, it always display the login page but IN MY CASE this login page is not required for internal users.
So pls guide me on how to setup/configure the above.
If you keep user authentication outside of QV (where it belongs, outside) you can let Windows take care of identifying an unknown user. Whenever someone tries to access an AD resource without prior authentication, a login dialog will popup. Most browsers know how to handle this kind of "mandatory login". An external user authenticates using his/her AD credentials (EXTERNAL domain. Note that both AD domains do need a Trust-relationship, and QVS server resources like the QlikView AP must be available to users from both domains) and once properly verified, can get through to the AP via SSO.
You're lucky that both groups of users are defined in an AD directory. Makes things alot simpler.
If you want to use the default QVS login page, it should work more or less the same. A web form will always be displayed, whether a user has already been authenticated (and can get in automatically through SSO) or not.