Quest ID Mapper

Current:1.2.8 (2017-11-28)
For QAS:3.0 or later
  • Linux i386
  • Linux x86_64
  • Solaris sparc
  • Solaris x86
  • HP-UX pa
  • AIX ppc
Licence:Resource Central

Quest's Samba Identity Mapper (vasidmap) provides Samba servers with accurate identity information for Unix-enabled Active Directory users to ensure proper file system access controls for Samba servers that are joined to an Active Directory domain. Vasidmap plugs into Samba's idmap interface, resolving queries for user security information by using Quest Authentication Services' (QAS) Active Directory connections and caches. vasidmap should be used with all installations of Samba where QAS is installed — especially for servers using Authentication Services' Unix personality management feature.

Quick installation instructions

  1. Ensure that you have Samba installed; we recommend using at least version 3.3.16 of your operating system's Samba package. The Quest ID Mapper should work with samba 3.0.28+ but versions below 3.3.16 are not supported.
  2. Ensure that the host is joined to Active Directory (vastool join)
  3. Install quest-vasidmap
  4. Run the vas-samba-config script:
    # /opt/quest/sbin/vas-samba-config
    and answer the questions asked.

Please see the installation guide for detailed instructions and troubleshooting.


Q: Will the Quest ID Mapper work with Samba packages from my operating system vendor or compiled from source?

A: Yes, both. The Quest ID Mapper was designed to integrate with Samba to provide additional benefits to customers using Samba and Quest Authentication Services together. Please make sure you are running at least version 3.3.16 of Samba before using the Quest ID Mapper.

Q: What are the benefits of using Quest ID Mapper with Samba?

A: The Quest ID Mapper can be used on servers that are accessed by Unix-enabled users via both local (shell) access and over Samba/CIFS shares. Using the ID mapper ensures file ownership matches the user's Unix-enabled attributes. Quest ID Mapper should not be used where non-Unix-enabled users access shares because it does not allocate IDs to non-Unix-enabled users. In that case either the idmap_rid or idmap_tdb providers should be used instead of Quest ID Mapper. See the Samba HOWTO chapter on identity mapping for further information.


Release: quest-vasidmap-1.2.8
Platform Filename Type Size Date MD5 checksum?
Other vasidmap releases
aix-53quest-vasidmap. kB2017-11-28b1bb9dec18e7e90f6d3db448d97fbb7d
hpux-ia64quest-vasidmap-1.2.8.ia64.depotpackage328 kB2017-11-28c8421f008e1e1e9144886c0b55d44cef
hpux-pa-11v1quest-vasidmap-1.2.8.hppa.depotpackage369 kB2017-11-283a078a1f99abf5d3c4fa6677f9af0121
linux-ia64quest-vasidmap-1.2.8-1.ia64.rpmpackage83 kB2017-11-282c4ecacfc0000c8b920c7df95154ebf8
linux-ppcquest-vasidmap-1.2.8-1.ppc.rpmpackage69 kB2017-11-2897dd3421e1966c1c3fb0621d33091c7f
linux-s390xquest-vasidmap-1.2.8-1.s390x.rpmpackage79 kB2017-11-28bce3caea99764ec9f195896f27fa76a8
linux-s390quest-vasidmap-1.2.8-1.s390.rpmpackage76 kB2017-11-28c6c0051063c63d9690656d2866e4a364
linux-x86_64quest-vasidmap-1.2.8-1.x86_64.rpmpackage79 kB2017-11-2839b2fe075d767ebb74c3124e42b18e88
quest-vasidmap_1.2.8-1_amd64.debpackage76 kB2017-11-28181d4c1070a90317306deda28c6a2bda
linux-x86quest-vasidmap-1.2.8-1.i386.rpmpackage56 kB2017-11-28ec6059ddeaea40b6b9153e482398473a
quest-vasidmap_1.2.8-1_i386.debpackage52 kB2017-11-285125cba26d1e2845c544220e16869fd4
osxquest-vasidmap-1.2.8.dmgpackage60 kB2017-11-28c4203d043c45ee94d99fed55906f7ceb
solaris-sparcQSFTidmap-1.2.8-sparc.pkgpackage224 kB2017-11-28472789b19d0de5d7bd0b3f7522402412
solaris-x86QSFTidmap-1.2.8-i386.pkgpackage215 kB2017-11-2858d59b7b05150034b155e1d9f8360b87
sourcequest-vasidmap-1.2.8.tar.gzsource205 kB2017-11-2844379936c86231f93a3b52c9e3da6b02

Compiling the vasidmap package from source requires the Authentication Services SDK to be installed. The SDK can be found in the SDK subdirectory directory of the Quest Authentication Services Installation CD.