Skip to main content

Turn OFF Password Expiry / Aging - CentOS / Ubuntu

Removing Password aging on centos is simple using ‘chage’ command change age
Below is a before and after command information.
 [ahmed@ahmed-on-edge:~$ chage -help
Usage: chage [options] LOGIN
Options:
 -d, --lastday LAST_DAY        set date of last password change to LAST_DAY
 -E, --expiredate EXPIRE_DATE  set account expiration date to EXPIRE_DATE
 -h, --help                    display this help message and exit
 -I, --inactive INACTIVE       set password inactive after expiration
                             to INACTIVE
 -l, --list                    show account aging information
 -m, --mindays MIN_DAYS        set minimum number of days before password
                             change to MIN_DAYS
 -M, --maxdays MAX_DAYS        set maximim number of days before password
                             change to MAX_DAYS
 -R, --root CHROOT_DIR         directory to chroot into
 -W, --warndays WARN_DAYS      set expiration warning days to WARN_DAYS

 ahmed@ahmed-on-edge:~$
Lets Execute the below command to find more information about our server.
 [ahmed@localhost ~]$ chage -l ahmed
 Last password change : Apr 29, 2014
 Password expires : Jun 28, 2014
 Password inactive : never
 Account expires : never
 Minimum number of days between password change : 7
 Maximum number of days between password change : 60
 Number of days of warning before password expires : 7
Command which we need to run
 [ahmed@localhost ~]$ sudo chage -I -1 -m 0 -M 99999 -E -1 [username]
 [ahmed@localhost ~]$ sudo chage -I -1 -m 0 -M 99999 -E -1 ahmed
After run - 
 [ahmed@localhost ~]$ chage -l ahmed
 Last password change : Apr 29, 2014
 Password expires : never
 Password inactive : never
 Account expires : never
 Minimum number of days between password change : 0
 Maximum number of days between password change : 99999
 Number of days of warning before password expires : -1
​
Labels:

Comments

Post a Comment

Popular posts from this blog

Zabbix History Table Clean Up

Zabbix history table gets really big, and if you are in a situation where you want to clean it up. Then we can do so, using the below steps. Stop zabbix server. Take table backup - just in case. Create a temporary table. Update the temporary table with data required, upto a specific date using epoch . Move old table to a different table name. Move updated (new temporary) table to original table which needs to be cleaned-up. Drop the old table. (Optional) Restart Zabbix Since this is not offical procedure, but it has worked for me so use it at your own risk. Here is another post which will help is reducing the size of history tables - http://zabbixzone.com/zabbix/history-and-trends/ Zabbix Version : Zabbix v2.4 Make sure MySql 5.1 is set with InnoDB as innodb_file_per_table=ON Step 1 Stop the Zabbix server sudo service zabbix-server stop Script. echo "------------------------------------------" echo " 1. Stopping Zabbix Server ...
1 comment
Read more

Installing Zabbix Version 2.4 Offline (Zabbix Server without Internet).

There might be situations where you have a remote/zabbix server which does not have internet connectivity, due to security or other reasons. So we create a custom repo on the remote/zabbix server so that we can install zabbix using rpms Here is how we are planning to do this. Download all the dependency rpms on a machine which has internet connection, using yum-downloadonly or repotrack . Transfer all the rpms to the remote server. Create a repo on the remote server. Update yum configuration. Install. NOTE: This method can be used to install any application, but here we have used zabbix as we had this requirement for a zabbix server. Download dependent rpms . On a machine which has internet connection install the package below. And download all the rpms . Make sure the system are similar (not required to be identical - At-least the OS should be of same version) mkdir /zabbix_rpms yum install yum-downloadonly Downloading all the rpms to location /zabbix_rpms/ ,...
1 comment
Read more

Access Filter in SSSD `ldap_access_filter` [SSSD Access denied / Permission denied ]

Access Filter Setup with SSSD ldap_access_filter (string) If using access_provider = ldap , this option is mandatory. It specifies an LDAP search filter criteria that must be met for the user to be granted access on this host. If access_provider = ldap and this option is not set, it will result in all users being denied access. Use access_provider = allow to change this default behaviour. Example: access_provider = ldap ldap_access_filter = memberOf=cn=allowed_user_groups,ou=Groups,dc=example,dc=com Prerequisites yum install sssd Single LDAP Group Under domain/default in /etc/sssd/sssd.conf add: access_provider = ldap ldap_access_filter = memberOf=cn=Group Name,ou=Groups,dc=example,dc=com Multiple LDAP Groups Under domain/default in /etc/sssd/sssd.conf add: access_provider = ldap ldap_access_filter = (|(memberOf=cn=System Adminstrators,ou=Groups,dc=example,dc=com)(memberOf=cn=Database Users,ou=Groups,dc=example,dc=com)) ldap_access_filter accepts standa...
1 comment
Read more