Configuring Veritas Operations Manager (VOM) to use Operating System (OS) based Lightweight Directory Authentication Protocol (LDAP) authentication

Article:HOWTO53190  |  Created: 2011-05-22  |  Updated: 2012-04-13  |  Article URL http://www.symantec.com/docs/HOWTO53190
Article Type
How To

Product(s)



BACKGROUND

 

It is beyond the scope of this document to present details on how to configure an OS to allow logins to use LDAP or Active Directory (AD) domain authentication.  The focus of this document is to configure VOM to use OS-based LDAP and/or AD (both will be referred to as LDAP) authentication.  In other words, if a UNIX host is configured to use LDAP as an authentication method, this document will present VOM configuration details to allow non-root logins to authenticate in VOM.

 

TECHNICAL INFORMATION

The following example uses the ldaplist command to search the LDAP database for the members of a group.

 

 (note: ldaplist is not a VOM command and is part of the OS or LDAP package)

 

# ldaplist -l group cisdefault
dn: cn=cisdefault,ou=Group,dc=unix,dc=xxxxxxx,dc=com
        gidNumber: 1086
        objectClass: posixGroup
        objectClass: top
        cn: cisdefault
dn: cn=eudefault,ou=Group,dc=unix,dc=xxxxx,dc=com
        memberUid: xxxxxxx
        gidNumber: 19786
        objectClass: posixGroup
        objectClass: top
        cn: cisdefault
        cn: eudefault

 

# ldaplist -l group dba  

     
dn: cn=dba,ou=Group,dc=unix,dc=xxxxxx,dc=com
        objectClass: posixGroup
        objectClass: top
        memberUid: abcdefg (an example)
        gidNumber: 3020
        cn: dba
 

This next two examples show how the OS recognizes group membership as presented by LDAP.  The OS command id -a [login] will be used to validate that the OS has the capability to recognize LDAP structured groups.  If so, these groups can be configured as VOM Security Groups for non-root authentication

/home/xxxxxxx ># id -a
uid=113025(xxxxxxx) gid=1086(cisdefault) groups=1086(cisdefault),3020(dba),1283(oracledba),1031(dba-usto),3123(dba-admin-dev)
 
/home/yyyyyyy># id -a
uid=109869(yyyyyyy) gid=1086(cisdefault) groups=1086(cisdefault),14(sysadmin),3523(cda108),10120(sdfrootr),10122(sdfinflr)

(note: this user is not a member of group dba)
 

In the example above for user xxxxxxx, he belongs to the LDAP groups cisdefault and dba.  The next step is to create Security Groups in VOM (dba).

(VOM Security Group names need to match the LDAP group name as bolded above; case sensitive)

 

1)  Open the Security Groups interface.

2)  Create a new Security Group.

 

3)  Define the Security group (click question mark icons or Help button for additional details)

 

 

4)  Example of newly created Security Groups

 

Note: the domain type used will be "unixpwd" so VOM will retreive group information as the OS knows it (which is demonstrated by the id -a commands above.

 

This method requires that the OS has been preconfigured for direct LDAP access (which typically is well documented per site and/or placed on build images).  This method allows VOM to take advantage of the OS-based LDAP interface for LDAP access without the need to configure VOM to discover the LDAP server.  In the event there is a site change to the LDAP configuration/access, OS-based access will likely be part of that change process allowing VOM access to continue working.  Otherwise,  if a site access change occurred, VOM would likely need to be reconfigured to reflect the change.

 

===============================================================

 

The following entries are examples that indicate the OS is configured to interface to LDAP for authentication (Linux examples are used here).

 

# grep -i ldap nsswitch.conf
passwd: files ldap
shadow: files ldap
group:  files ldap
netgroup:       files ldap
# grep -i ldap services
ldap            389/tcp
ldap            389/udp
ldaps           636/tcp                         # LDAP over SSL
ldaps           636/udp                         # LDAP over SSL
www-ldap-gw     1760/tcp                        # www-ldap-gw
www-ldap-gw     1760/udp                        # www-ldap-gw
msft-gc-ssl     3269/tcp                        # Microsoft Global Catalog with LDAP/SSL
msft-gc-ssl     3269/udp                        # Microsoft Global Catalog with LDAP/SSL
ldap-admin      3407/tcp                        # LDAP admin server port
ldap-admin      3407/udp                        # LDAP admin server port
usto-dapp-vcs01:Linux:/etc >#

===============================================================

# grep -i ldap.xxxxx.com /etc/*
ldap.conf:uri ldap://ldap.xxxxxx.com:1389/


# cat /etc/ldap.conf
# @(#)$Id: ldap.conf,v 1.38 2006/05/15 08:13:31 lukeh Exp $
#
# This is the configuration file for the LDAP nameservice
# switch library and the LDAP PAM module.
#
# The man pages for this file are nss_ldap(5) and pam_ldap(5)
#
# PADL Software
# http://www.padl.com
#

# Your LDAP server. Must be resolvable without using LDAP.
# Multiple hosts may be specified, each separated by a
# space. How long nss_ldap takes to failover depends on
# whether your LDAP client library supports configurable
# network or connect timeouts (see bind_timelimit).
#host 127.0.0.1

# The distinguished name of the search base.
base dc=unix,dc=amgen,dc=com

# Another way to specify your LDAP server is to provide an
# uri with the server name. This allows to use
# Unix Domain Sockets to connect to a local LDAP Server.
#uri ldap://127.0.0.1/
#uri ldaps://127.0.0.1/
#uri ldapi://%2fvar%2frun%2fldapi_sock/
# Note: %2f encodes the '/' used as directory separator

# The LDAP version to use (defaults to 3
# if supported by client library)
#ldap_version 3

# The distinguished name to bind to the server with.
# Optional: default is to bind anonymously.
#binddn cn=proxyuser,dc=example,dc=com

# The credentials to bind with.
# Optional: default is no credential.
#bindpw secret

# The distinguished name to bind to the server with
# if the effective user ID is root. Password is
# stored in /etc/ldap.secret (mode 600)
#rootbinddn cn=manager,dc=example,dc=com

# The port.
# Optional: default is 389.
#port 389

# The search scope.
#scope sub
#scope one
#scope base

# Search timelimit
#timelimit 30
timelimit 120

# Bind/connect timelimit
#bind_timelimit 30
bind_timelimit 120

# Reconnect policy: hard (default) will retry connecting to
# the software with exponential backoff, soft will fail
# immediately.
#bind_policy hard

# Idle timelimit; client will close connections
# (nss_ldap only) if the server has not been contacted
# for the number of seconds specified below.
#idle_timelimit 3600
idle_timelimit 3600

# Filter to AND with uid=%s
#pam_filter objectclass=account

# The user ID attribute (defaults to uid)
#pam_login_attribute uid

# Search the root DSE for the password policy (works
# with Netscape Directory Server)
#pam_lookup_policy yes

# Check the 'host' attribute for access control
# Default is no; if set to yes, and user has no
# value for the host attribute, and pam_ldap is
# configured for account management (authorization)
# then the user will not be allowed to login.
#pam_check_host_attr yes

# Check the 'authorizedService' attribute for access
# control
# Default is no; if set to yes, and the user has no
# value for the authorizedService attribute, and
# pam_ldap is configured for account management
# (authorization) then the user will not be allowed
# to login.
#pam_check_service_attr yes

# Group to enforce membership of
#pam_groupdn cn=PAM,ou=Groups,dc=example,dc=com

# Group member attribute
#pam_member_attribute uniquemember

# Specify a minium or maximum UID number allowed
#pam_min_uid 0
#pam_max_uid 0

# Template login attribute, default template user
# (can be overriden by value of former attribute
# in user's entry)
#pam_login_attribute userPrincipalName
#pam_template_login_attribute uid
#pam_template_login nobody

# HEADS UP: the pam_crypt, pam_nds_passwd,
# and pam_ad_passwd options are no
# longer supported.
#
# Do not hash the password at all; presume
# the directory server will do it, if
# necessary. This is the default.
#pam_password clear

# Hash password locally; required for University of
# Michigan LDAP server, and works with Netscape
# Directory Server if you're using the UNIX-Crypt
# hash mechanism and not using the NT Synchronization
# service.
#pam_password crypt

# Remove old password first, then update in
# cleartext. Necessary for use with Novell
# Directory Services (NDS)
#pam_password clear_remove_old
#pam_password nds

# RACF is an alias for the above. For use with
# IBM RACF
#pam_password racf

# Update Active Directory password, by
# creating Unicode password and updating
# unicodePwd attribute.
#pam_password ad

# Use the OpenLDAP password change
# extended operation to update the password.
#pam_password exop

# Redirect users to a URL or somesuch on password
# changes.
#pam_password_prohibit_message Please visit http://internal to change your password.

# RFC2307bis naming contexts
# Syntax:
# nss_base_XXX          base?scope?filter
# where scope is {base,one,sub}
# and filter is a filter to be &'d with the
# default filter.
# You can omit the suffix eg:
# nss_base_passwd       ou=People,
# to append the default base DN but this
# may incur a small performance impact.
#nss_base_passwd        ou=People,dc=example,dc=com?one
#nss_base_shadow        ou=People,dc=example,dc=com?one
#nss_base_group         ou=Group,dc=example,dc=com?one
#nss_base_hosts         ou=Hosts,dc=example,dc=com?one
#nss_base_services      ou=Services,dc=example,dc=com?one
#nss_base_networks      ou=Networks,dc=example,dc=com?one
#nss_base_protocols     ou=Protocols,dc=example,dc=com?one
#nss_base_rpc           ou=Rpc,dc=example,dc=com?one
#nss_base_ethers        ou=Ethers,dc=example,dc=com?one
#nss_base_netmasks      ou=Networks,dc=example,dc=com?ne
#nss_base_bootparams    ou=Ethers,dc=example,dc=com?one
#nss_base_aliases       ou=Aliases,dc=example,dc=com?one
#nss_base_netgroup      ou=Netgroup,dc=example,dc=com?one

# Just assume that there are no supplemental groups for these named users
nss_initgroups_ignoreusers root,ldap,named,avahi,haldaemon,dbus,radvd,tomcat,radiusd,news,mailman,nscd,gdm

# attribute/objectclass mapping
# Syntax:
#nss_map_attribute      rfc2307attribute        mapped_attribute
#nss_map_objectclass    rfc2307objectclass      mapped_objectclass

# configure --enable-nds is no longer supported.
# NDS mappings
#nss_map_attribute uniqueMember member

# Services for UNIX 3.5 mappings
#nss_map_objectclass posixAccount User
#nss_map_objectclass shadowAccount User
#nss_map_attribute uid msSFU30Name
#nss_map_attribute uniqueMember msSFU30PosixMember
#nss_map_attribute userPassword msSFU30Password
#nss_map_attribute homeDirectory msSFU30HomeDirectory
#nss_map_attribute homeDirectory msSFUHomeDirectory
#nss_map_objectclass posixGroup Group
#pam_login_attribute msSFU30Name
#pam_filter objectclass=User
#pam_password ad

# configure --enable-mssfu-schema is no longer supported.
# Services for UNIX 2.0 mappings
#nss_map_objectclass posixAccount User
#nss_map_objectclass shadowAccount user
#nss_map_attribute uid msSFUName
#nss_map_attribute uniqueMember posixMember
#nss_map_attribute userPassword msSFUPassword
#nss_map_attribute homeDirectory msSFUHomeDirectory
#nss_map_attribute shadowLastChange pwdLastSet
#nss_map_objectclass posixGroup Group
#nss_map_attribute cn msSFUName
#pam_login_attribute msSFUName
#pam_filter objectclass=User
#pam_password ad

# RFC 2307 (AD) mappings
#nss_map_objectclass posixAccount user
#nss_map_objectclass shadowAccount user
#nss_map_attribute uid sAMAccountName
#nss_map_attribute homeDirectory unixHomeDirectory
#nss_map_attribute shadowLastChange pwdLastSet
#nss_map_objectclass posixGroup group
#nss_map_attribute uniqueMember member
#pam_login_attribute sAMAccountName
#pam_filter objectclass=User
#pam_password ad

# configure --enable-authpassword is no longer supported
# AuthPassword mappings
#nss_map_attribute userPassword authPassword

# AIX SecureWay mappings
#nss_map_objectclass posixAccount aixAccount
#nss_base_passwd ou=aixaccount,?one
#nss_map_attribute uid userName
#nss_map_attribute gidNumber gid
#nss_map_attribute uidNumber uid
#nss_map_attribute userPassword passwordChar
#nss_map_objectclass posixGroup aixAccessGroup
#nss_base_group ou=aixgroup,?one
#nss_map_attribute cn groupName
#nss_map_attribute uniqueMember member
#pam_login_attribute userName
#pam_filter objectclass=aixAccount
#pam_password clear

# Netscape SDK LDAPS
#ssl on

# Netscape SDK SSL options
#sslpath /etc/ssl/certs

# OpenLDAP SSL mechanism
# start_tls mechanism uses the normal LDAP port, LDAPS typically 636
#ssl start_tls
#ssl on

# OpenLDAP SSL options
# Require and verify server certificate (yes/no)
# Default is to use libldap's default behavior, which can be configured in
# /etc/openldap/ldap.conf using the TLS_REQCERT setting.  The default for
# OpenLDAP 2.0 and earlier is "no", for 2.1 and later is "yes".
#tls_checkpeer yes

# CA certificates for server certificate verification
# At least one of these are required if tls_checkpeer is "yes"
#tls_cacertfile /etc/ssl/ca.cert
#tls_cacertdir /etc/ssl/certs

# Seed the PRNG if /dev/urandom is not provided
#tls_randfile /var/run/egd-pool

# SSL cipher suite
# See man ciphers for syntax
#tls_ciphers TLSv1

# Client certificate and key
# Use these, if your server requires client authentication.
#tls_cert
#tls_key

# Disable SASL security layers. This is needed for AD.
#sasl_secprops maxssf=0

# Override the default Kerberos ticket cache location.
#krb5_ccname FILE:/etc/.ldapcache

# SASL mechanism for PAM authentication - use is experimental
# at present and does not support password policy control
#pam_sasl_mech DIGEST-MD5
uri ldap://ldap.xxxxx.com:1389/
ssl no
tls_cacertdir /etc/openldap/cacerts
pam_password md5
 

 

 

 



Article URL http://www.symantec.com/docs/HOWTO53190


Terms of use for this information are found in Legal Notices