Quest Software

Quest ID Mapper

vasidmap
Current:quest-vasidmap-1.2.0 (2009-11-25)
For QAS:3.0 or later
Platforms:
  • Linux i386
  • Linux x86_64
  • Solaris sparc
  • Solaris x86
  • HP-UX pa
  • AIX ppc
Resources:
License:Resource Central
Development:

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.0.28 of your operating system's Samba package. The Quest ID Mapper does not support versions older than 3.0.28.
  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.

FAQ

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.0.28 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.

Download

Release: quest-vasidmap-1.2.0
Platform Filename Type Size Date MD5 checksum?
Other vasidmap releases
aix-43quest-vasidmap.1.2.0.0.bffpackage5.0 MB2009-12-04e7c125ecaaf25cef2f2b2eb84306f243
aix-51quest-vasidmap.1.2.0.0.bffpackage5.0 MB2009-12-04e7c125ecaaf25cef2f2b2eb84306f243
aix-53quest-vasidmap.1.2.0.0.bffpackage5.0 MB2009-12-04e7c125ecaaf25cef2f2b2eb84306f243
hpux-ia64quest-vasidmap-1.2.0.ia64.depotpackage246 kB2009-12-042797af62a530b79d39fadd9e781a39db
hpux-paquest-vasidmap-1.2.0.hppa.depotpackage236 kB2009-12-04f72ea47bb7d167c93856483b7c949f03
linux-glibc23-ppc64quest-vasidmap-1.2.0-1.ppc.rpmpackage46 kB2009-12-043285f4e7e42a276a210b424e1933f145
linux-x86_64quest-vasidmap-1.2.0-1.x86_64.rpmpackage50 kB2009-11-25657375bc08c88e8837006ad9cefad595
quest-vasidmap_1.2.0-2_amd64.debpackage42 kB2009-12-04b437c854838daa6d5e6f14fab798abd7
linux-x86quest-vasidmap-1.2.0-1.i386.rpmpackage67 kB2009-11-253845e80019354815e47d76457892d7e2
quest-vasidmap_1.2.0-2_i386.debpackage63 kB2009-12-04260562d3cffd2853c8ae8a3a987e90a1
solaris26-sparcQSFTidmap-1.2.0-sparc.pkgpackage206 kB2009-12-0404c42c65108dd5ddd0fd8773ec8bfd16
solaris8-sparcQSFTidmap-1.2.0-sparc.pkgpackage206 kB2009-12-0404c42c65108dd5ddd0fd8773ec8bfd16
solaris8-x86QSFTidmap-1.2.0-i386.pkgpackage212 kB2009-12-047be8a1661928fd892fbc865f02408d41
sourcequest-vasidmap-1.2.0.tar.gzsource157 kB2009-12-04952c1a6a9d68f871561d3d7b89a379bd

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.