User Guide Appendix
APconnections, Inc. // 303.997.1300 // www.netequalizer.com
Page 117 of 120
rev. 20170131
© 2014-2017 APconnections, Inc. All Rights Reserved
version 8.4
Appendix 8 – NetEqualizer Directory Integration (NDI)
This appendix is for customers that are interested in setting up NetEqualizer Directory
Integration (NDI). NDI provides usernames to the NetEqualizer from your back-end
directory server, which then can be used to enhance various features within the
NetEqualizer. Features supported include NDI (Level 1) and Named Quotas (Level 2), which
will be discussed in detail below.
Background on NetEqualizer Directory Integration (NDI)
Over the years we have received requests from customers to integrate with their back-end
domain controller systems, such as Microsoft Active Directory and other server
implementations of LDAP (Apache, IBM Tivoli, etc.). We have always felt that this would be
a powerful combination, as Directory Integration has the obvious benefit of utilizing known
usernames from your system to identify data flows & activity in the NetEqualizer, rather
than IP addresses. As you can imagine, this could make it much easier to trace activity
back to a particular user.
As of
Software Update 7.0
, we are offering NetEqualizer Directory Integration (NDI) with
our initial set of functionality – think of this as “Level 1” capability. We are also offering a
Beta Test
of our first additional “Level 2” functionality, Named Quotas.
Note: There is a one-time initial activation and set-up charge for NetEqualizer Directory Integration
(NDI). Once set-up, NDI software itself is covered under NSS; to get future releases, you will need to
be current on your NSS. Check our
price list
for details on the NDI activation charge.
Setting up NetEqualizer Directory Integration (Level 1)
NDI Level 1 consists of a generic API that can be used by customers once they implement a
function on their domain controller (DC) server. Once set-up and configured, the NDI API
provides names and associated IP addresses to the NetEqualizer. The NetEqualizer will
eventually enable the use of names in a variety of reports, as we learn where they are most
useful. In Level 1, we will start by adding names to our basic live snapshot of equalizing
activity, the “Active Connections” Report.
1.
On the back-end Domain Controller (DC) Server
You will need to first write a function (cgi or php script) on your back-end domain controller
(DC) server (which can be any LDAP implementation) that takes an IP address as an
argument and returns a clean username. If the IP is not recognized, it should return the
string “unknown”. This function will be called by the NDI API on your NetEqualizer.
Note: Originally we had done some work to write the function to integrate Active Directory, but found
that each customer in our Beta had a unique implementation, rendering a shared function useless.
We have decided for GA to have each customer implement access to their unique domain information.
If you have questions regarding this function, please contact
support@apconnections.net
or call
303.997.1300 x102. We can share what we have learned from our Beta work.
2.
On the NetEqualizer
You will need to create a text file containing a list of IP subnets to search, as show below.