Frequently Asked Questions
Does VIS support Kerberos and/or NTLM/Negotiate authentications?
Yes, VIS supports Kerberos, NTLM and Negotiate as authentication options on both the listing side as well as the back-end connection sides.
Can I get a demo/evaluation version of VIS?
Yes. Please fill out a demo form with your contact information.
What data stores can the Virtual Identity Server connect to?
The Virtual Identity Server supports a number of data stores directly with out of the box adapters. Additionally, a customer or integrator can create adapters utilizing our built-in extensibility.
Is your product FIPS compliant?
Yes. Our software is running in both non-secure and secure government networks.
Does VIS support caching?
Yes. There are multiple caching options with VIS. Caching can be configured on an object class by object class basis, with a time to live and cache size as well. Most organizations in most situations, however, do not need to use caching.
Do you SharePoint integration?
We support WSS 3.0, SharePoint 2007, 2010 & 2013.
Do you support server virtualization like HyperV or VMWARE?
Does VIS come as a 64-bit application?
Yes. VIS is now only offered in a 64-bit version of the product.
Is VIS supported on Windows 2012?
Yes. The Virtual Identity Server is certified on both Windows Server 2012 and Windows Server 2012 R2.
Is VIS supported on Windows 2008?
Yes. The Virtual Identity Server is certified on both Windows Server 2008 and Windows Server 2008 R2.
Is VIS supported on Windows 2003?
Yes. The Virtual Identity Server is certified on both Windows Server 2003.
What additional software requirements does VIS have?
VIS was written in Microsoft’s .NET programming language and utilizes the .NET 4.5 Framework.
What encryption algorithms does your product support?
VIS can encrypt this information with any of the following algorithms Triple-DES (3DES), AES, RIJNDAEL and BLOWFISH
Does your product store any un-encrypted user id information or passwords?
Individual entries, such as bind accounts and passwords or even the entire XML file can be optionally encrypted using the GUI.
Is there a GUI to maintain the XML file?
Yes. There is a Windows GUI that provides an easy interface to edit the XML file. You can also edit the XML file manually if you prefer.
Can this XML file be shared across multiple VIS servers?
Yes. Multiple VIS server instances can all share the same XML file.
How does VIS store configuration information?
The product configuration is stored in one XML file, making the product extremely easy to configure and migrate.
What TCP/IP port does VIS run/listen on?
VIS can be configured to run on any port you choose provided another application is not using that port. You can choose the standard LDAP port of 389 or 636 (SSL).
Can VIS be load balanced?
Yes. VIS can be placed behind a load balancer (either software or hardware), allowing for a fail-over and load balancing configuration for the applications that connect to VIS. In addition, the connections that VIS makes to connected directories can be load balanced as well.
What types of listeners does VIS support?
VIS can listen via LDAP v3, REST Web Service, PowerShell out of the box, but can be extended to listen via any protocol/method desired using the API’s. With 3rd party ODBC/ADO.NET Drivers, SQL calls can also be made.
How long does it take to install and configure VIS?
VIS installs in minutes, using a standard MSI/setup.exe. After installing the binary files, a wizard guides you through the configuration of the product. While the Virtual Identity Server has the most comprehensive features of any virtual directory product on the market, a key differentiator is how easy the product is to install and configure.