04-20-2010
Adding LDAP users to local groups AIX
I am having the same problem and creating groups with the same GUIDs in Active Directory isn't a practical solution.
I have read forum updates elsewhere that discuss using PAM modules to do this successfully on Linux so maybe that's directly translatable to AIX.
7 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hey,
I have few Questions :
1. How to Check/Find who all are the users accessing the server using their id ?
2. How to Check who is the active user or non active user (whose id exists but the access privileges has been removed) ?
I am presently using AIX5.3 as a server.
Please suggest... (3 Replies)
Discussion started by: varungupta
3 Replies
2. UNIX for Advanced & Expert Users
Hello, I asked this question in the AIX subforum but never received an answer, probably because the AIX forum is not that heavily trafficked. Anyway, here it is..
I have never had any issues like this when compiling applications from source. When I try to compile samba-3.5.0pre2, configure runs... (9 Replies)
Discussion started by: raidzero
9 Replies
3. AIX
First, let me start off saying this is not spam. This is me trying to help out other AIX Admins with MS AD servers. If it is not applicable to you, someone else will find it useful.
As long as the "KDC" service is running on your AD server, these steps should work. There should be no... (3 Replies)
Discussion started by: kah00na
3 Replies
4. Solaris
we want to allow user to FTP files into a directory, and then the program (PLSQL) will read and process the file, and then move the file to other directory for archiving.
the user id: uftp1, group: ftp
the program run in oracle database, thus have the user Id: oraprod, group: dba
how to... (2 Replies)
Discussion started by: siakhooi
2 Replies
5. UNIX for Advanced & Expert Users
Hi,
I have created a shared directory on /home, where all users on a certain group have read, write and execute permissions.
I did this using
chmod -R g+rwx /home/shared/
The problem is, when a particular user creates a directory within /home/shared, other users are not able to write to... (8 Replies)
Discussion started by: lost.identity
8 Replies
6. AIX
Hi. Ive recently upgraded Samba on an AIX server to Samba 4. The aim is to allow a specific group of Windows AD users to access some AIX file shares (with no requirement to enter passwords) - using AD to authenticate.
Currently I have:
Samba 4 installed ( and 3 daemons running)
Installed... (1 Reply)
Discussion started by: linuxsnake
1 Replies
7. AIX
I am running AIX 7.1 and currently we have samba 3.6.25 installed on the server. As it stands some AIX folders are shared that can be accessed by certain Windows users.
The problem is that since Windows 10 the guest feature no longer works so users have to manually type in their Windows login/pwd... (14 Replies)
Discussion started by: linuxsnake
14 Replies
LEARN ABOUT OPENSOLARIS
ad
ad(5) Standards, Environments, and Macros ad(5)
NAME
ad - Active Directory as a naming repository
DESCRIPTION
Solaris clients can obtain naming information from Active Directory (AD) servers.
The Solaris system must first join an AD domain and then add the ad keyword to the appropriate entries in the nsswitch.conf(4) file. The
Solaris system joins the AD domain by using the kclient(1M) utility. The AD name service only supports the naming databases for passwd and
group.
Windows users are not able to log in. The user_attr(4) database has no entries for Windows users, and the passwd(1) command does not sup-
port the synchronization of user passwords with AD.
The Solaris AD client uses auto-discovery techniques to find AD directory servers, such as domain controllers and global catalog servers.
The client also uses the LDAP v3 protocol to access naming information from AD servers. The AD server schema requires no modification
because the AD client works with native AD schema. The Solaris AD client uses the idmap(1M) service to map between Windows security identi-
fiers (SIDs) and Solaris user identifiers (UIDs) and group identifiers (GIDs). User names and group names are taken from the sAMAccountName
attribute of the AD user and group objects and then tagged with the domain where the objects reside. The domain name is separated from the
user name or group name by the @ character.
The client uses the SASL/GSSAPI/KRB5 security model. The kclient utility is used to join the client to AD. During the join operation,
kclient configures Kerberos v5 on the client. See kclient(1M).
FILES
/etc/nsswitch.conf Configuration file for the name-service switch.
/etc/nsswitch.ad Sample configuration file for the name-service switch configured with ad, dns and files.
/usr/lib/nss_ad.so.1 Name service switch module for AD.
SEE ALSO
passwd(1), svcs(1), idmap(1M), idmapd(1M), kclient(1M), svcadm(1M), svccfg(1M), svccfg(1M), nsswitch.conf(4), user_attr(4), smf(5)
SunOS 5.11 22 Oct 2008 ad(5)