Protector uses the concept of Authentication Spaces when authenticating users. The Authentication Space tells the Protector master node which authentication service is able to validate a specific user's login credentials. Authentication requests are routed, by the master, to the proxy node responsible for communicating with the authentication service in question.
Although it is possible to nominate the master node as the proxy, it is often the case that the master node is either not in the required space or is of the wrong OS type. Consider the following scenario:
Here the Protector master node is responsible for nodes in three separate spaces, so a separate proxy is required to communicate with each authentication service. It is possible to have different authentication service types for each space.
- An Active Directory authentication space could be configured to point to the AD server ContosoDC.HV.local and could be named Contoso. Users in this AD domain must authenticate with Protector using <username>@Contoso. Here Contoso is used as an alias for ContosoDC.HV.local. If you want to use the full domain name then the authentication space must also be named using the full domain name.
- A Local Machine Accounts authentication space is configured to point to the computer TBell-Win7PC and could be named TBW7. Users with local accounts on the machine TBell-Win7PC must authenticate with Protector using <username>@TBW7. Here TBW7 is used as an alias for TBell-Win7PC. If you want to use the full computer name then the authentication space must also be named using the full computer name.