The thing is that on CentOS, redhat servers we have, we can login to local users and LDAP users, and when performing actions on users, it only affects local users.
If it's not possible to do it on AIX well... I'll have to find a workaround.
Location: on the road for work; home is private time
Posts: 456
Thanks Given: 10
Thanked 108 Times in 100 Posts
Maybe I do not understand the question. But, let's say michael exists in both LDAP and AIX domains.
To change the account michael 'locally' I would use:
# chuser -R files .... michael
And the same, or a different change on LDAP would be:
# chuser -R LDAP .... michael
However, I expect most changes using chuser -R LDAP ... michael will fail if your server only supports the RFC2307 DIT or LDIF specification (basically, what is found in /etc/passwd and /etc/group and the shadowed encryption of the password).
Basics:
when you ran the mksecldap command you configured the file /etc/security/ldap.cfg and arranged for the daemons to start.
Look at this section on your server - I do not have LDAP configured so all are commented out - you should have a few uncommented.
Line numbers are approximate!
unix_auth is default, and preferred
Preferred is "system" and update /etc/security/login.cfg to use sssh256
These are the user attributes defining the schema used. Are these uncommented? What do they point too?
And finally, for the basics: what is active/inactive here?
---------- Post updated at 02:17 PM ---------- Previous update was at 02:14 PM ----------
Quote:
Originally Posted by AIX_user_324891
The thing is that on CentOS, redhat servers we have, we can login to local users and LDAP users, and when performing actions on users, it only affects local users.
If it's not possible to do it on AIX well... I'll have to find a workaround.
I expect it is using, by default, the same schema (attribute mapping) in LDAP and it does in it's local files.
AIX includes an LDAP server at no additional charge for AIX user admin. Maybe using that will get you 90% of the way. You can still configure AIX to go to a 'foreign' LDAP server for "login" verification.
Last edited by MichaelFelt; 11-25-2015 at 09:18 AM..
Reason: typo
AIX introduced a new alternative authentication control attribute "authcontroldomain" from AIX 6.1 Tl07 and 71 Tl01 releases. When this attribute is set, SYSTEM and registry attributes are stored or retrieved from that database. For local users, SYSTEM and registry attribute are stored in /etc/security/user file irrespective of the authcontroldomain value.
The authcontroldomain attribute needs to be defined with a loadmodule name which is defined in the /etc/methods.cfg or /usr/lib/security/methods.cfg file. This attribute needs to be defined in the /etc/security/login.cfg file under the usw stanza.
authcontroldomain attribute can be set for a system as using the chsec command. For example:
Quick Test: LDAP and local User Login works fine without further specifying SYSTEM or registry.
Security load modules are defined in /usr/lib/security/methods.cfg file. User identification is done based on order in, which load modules are defined in methods.cfg file. Local load module information is not defined in the /usr/lib/security/methods.cfg file. However, the user information will be verified first in local module; then the order that is defined in methods.cfg file will follow.
These 2 Users Gave Thanks to -=XrAy=- For This Post:
Location: on the road for work; home is private time
Posts: 456
Thanks Given: 10
Thanked 108 Times in 100 Posts
Thanks -=XrAy=-, for reminding me that sometimes developerworks has new information, not just rehashed.
AIX_user_324891 - lots of feedback in both directions. I am still not sure exactly what you want to achieve. If I was at your location I would ask for a demonstration of what you do on your linux servers - and then think about how I would approach that on AIX. Security is Managing Detail - without control of the details security is not - imho. So, describing, in definitive terms helps an old fool like myself (fool because I play blind (I prefer saying I try to not assume) to things everyone else sees as self-evident).
This User Gave Thanks to MichaelFelt For This Post:
i found a solution that seems to work (in my setup):
authcontroldomain attribute
AIX introduced a new alternative authentication control attribute "authcontroldomain" from AIX 6.1 Tl07 and 71 Tl01 releases. When this attribute is set, SYSTEM and registry attributes are stored or retrieved from that database. For local users, SYSTEM and registry attribute are stored in /etc/security/user file irrespective of the authcontroldomain value.
The authcontroldomain attribute needs to be defined with a loadmodule name which is defined in the /etc/methods.cfg or /usr/lib/security/methods.cfg file. This attribute needs to be defined in the /etc/security/login.cfg file under the usw stanza.
authcontroldomain attribute can be set for a system as using the chsec command. For example:
Quick Test: LDAP and local User Login works fine without further specifying SYSTEM or registry.
Regards
Security load modules are defined in /usr/lib/security/methods.cfg file. User identification is done based on order in, which load modules are defined in methods.cfg file. Local load module information is not defined in the /usr/lib/security/methods.cfg file. However, the user information will be verified first in local module; then the order that is defined in methods.cfg file will follow.
Thanks for you reply,
Its almost what i need, your solution looks good but now i think i've got a configuration problem , when i login to my ldap user via root (su ldap_user) it works, but when i try to login with a normal user i got an error message.
---------- Post updated at 09:15 AM ---------- Previous update was at 08:50 AM ----------
Quote:
Originally Posted by MichaelFelt
Thanks -=XrAy=-, for reminding me that sometimes developerworks has new information, not just rehashed.
AIX_user_324891 - lots of feedback in both directions. I am still not sure exactly what you want to achieve. If I was at your location I would ask for a demonstration of what you do on your linux servers - and then think about how I would approach that on AIX. Security is Managing Detail - without control of the details security is not - imho. So, describing, in definitive terms helps an old fool like myself (fool because I play blind (I prefer saying I try to not assume) to things everyone else sees as self-evident).
Here's a demonstation of what i can do on my linux servers :
First i've got a linux user in my LDAP server like this : uid=ldap_user,ou=linux_users,ou=other,o=other
When connecting to our CentOS server, i just do this :
Now on that vhzva03 if i grep /etc/passwd, i don't find the ldap_user (as expected)
When looking with a ldapsearch command ldapsearch -b "o=other" -x "(cn=ldap_user)"
Now with a useradd :
Now userdel:
As you can see, i can login via ssh, su to my ldap_user.
When performing account commands, only local users are affected.
ldap_user's Password:
Cannot su to "ldap_user" : Authentication is denied.
[/CODE]
Changing the default stanza to
seems to be a workaround. Now i can SU from an LDAP user to another LDAP user. If i try to delete a ldap user (as root), i get an error: 3004-698 Error committing changes to "ldap_user".
BUT: I noticed that the chsec command throw the same error.
So the use of authcontroldomain seems to be buggy. You/I will need do further tests.
Changing the default stanza to
seems to be a workaround. Now i can SU from an LDAP user to another LDAP user. If i try to delete a ldap user (as root), i get an error: 3004-698 Error committing changes to "ldap_user".
BUT: I noticed that the chsec command throw the same error.
So the use of authcontroldomain seems to be buggy. You/I will need do further tests.
Regards
Ok, i triied this, it looks like it work, hope the
Does not make some bugs anywhere
I'd like to add some x/linux-based servers to my current AIX-based TDS/SDS server community. Reading the Fine Install Guide (rtfig ?) I believe this may be covered by the section "Upgrade an instance of a previous version to a different computer" i.e. I'm going to install latest/greatest SDS on a... (4 Replies)
Hello,
i configured rhel linux 6 with AD directory to authorize windows users to connect on the system and it works.
i have accounts with high privileges (oracle for example) if an account is created on the AD server i would to block him.
I looked for how to do, for the moment all the... (3 Replies)
Hi,
I need to switch from local user to root user in a shell script.
I need to make it automated so that it doesn't prompt for the root password.
I heard the su command will do that work but it prompt for the password.
and also can someone tell me whether su command spawns a new shell or... (1 Reply)
Hi,
I have been asked to create a ksh script that will search against an LDAP directory from various HP-UX, SUSE, and AIX 5.3 and 6.1 machines. The objective is to verify the boxes are successfully authenticating users from the LDAP store. This is something I've never done, and I could use... (0 Replies)
Hi Gurus,
I have a script that requires me to switch from local user to root. Anyone who has an idea on this since when i switch user to root it requires me to input root password.
It seems that i need to use expect module here, but i don't know how to create the object for this.
... (1 Reply)
If I create a new user id test:
mkuser id=400 test
then I want it to LDAP user:
chuser -R LDAP SYSTEM=LDAP registry=LDAP test
It shows:
3004-687 User "test" does not exist.
How to do? (4 Replies)
Hi Friends,
I have this script for ftping files from AIX server to local windows xp.
#!/bin/sh
HOST='localsystem.net'
USER='myid_onlocal'
PASSWD='mypwd_onlocal'
FILE='file.txt' ##This is a file on server(AIX)
ftp -n $HOST <<END_SCRIPT
quote USER $USER
quote PASS $PASSWD
put $FILE... (1 Reply)
Besides doing some shell-script which loops through /etc/passwd, I was wondering if there was some command that would tell me, like an enhanced version of getent.
The Operating system is Solaris 10 (recent-ish revision) using Sun DS for LDAP. (5 Replies)
I am implementing LDAP on Linux based system using openldap.
My management objects to the idea that all individual users will authenticate against an LDAP server because “what if it is not available”
Their suggestion is that we run in parallel a set of local configured users and a set of LDAP... (1 Reply)