Adding RPMforge to Yum

The rpmforge repo package can be downloaded from the site below.

1. Launch Firefox and go to http://dag.wieers.com/rpm/FAQ.php#B2. Click on the package appropriate for your version of Red Hat Enterprise Linux or CentOS.

2. Choose Open with Software Installer (default) and click Ok.

3. The Installing packages window will appear. Click Apply to proceed.

4. Finally click Ok.

Lowering the RPMforge priority

Lowering the priority of the RPMforge repository will ensure that the base packages provided by RHEL/CentOS will not be replaced by a newer version from RPMforge.

1. Install the Yum priorities package using the command below.

yum install yum-priorities

2. Edit the file /etc/yum.repos.d/rpmforge.repo and add the line below.

priority=10

3. Test your configuration using the command below. You should see a priority protections message in the output.

yum check-update

Share This

History

Version 0.9-1.4.2

Released on June 7, 2009
[ download ]

• Domain name for Linux system accounts are now retrieved from the setting in SquirrelMail instead of being derived using the hostname command.
• Added option to disable LDAP referral chasing.

Version 0.9-1.4.1

Released on November 15, 2008
[ download ]

• Fixed Linux system account retrieval by detecting the domain name hostname command.
• Added option to set LDAP protocol version.
• Optimized the settings saving by.

Howtos

How to install the Retrieve User Data plugin in SquirrelMail

Share This

We recognize that privacy of your personal information is important. Here is information on what types of personal information we receive and collect when you use and visit this site, and how we safeguard your information. We never sell your personal information to third parties.

Log Files

As with most other websites, we collect and use the data contained in log files. The information in the log files include your IP (internet protocol) address, your ISP (internet service provider, such as AOL or Shaw Cable), the browser you used to visit our site (such as Internet Explorer or Firefox), the time you visited our site and which pages you visited throughout our site.

Cookies and Web Beacons

We do use cookies to store information, such as your personal preferences when you visit our site. This could include only showing you a popup once in your visit, or the ability to login to some of our features, such as forums.

We also use third party advertisements to support our site. Some of these advertisers may use technology such as cookies and web beacons when they advertise on our site, which will also send these advertisers (such as Google through the Google AdSense program) information including your IP address, your ISP, the browser you used to visit our site, and in some cases, whether you have Flash installed. This is generally used for geotargeting purposes (showing New York real estate ads to someone in New York, for example) or showing certain ads based on specific sites visited (such as showing cooking ads to someone who frequents cooking sites).

You can chose to disable or selectively turn off our cookies or third-party cookies in your browser settings, or by managing preferences in programs such as Norton Internet Security. However, this can affect how you are able to interact with our site as well as other websites. This could include the inability to login to services or programs, such as logging into forums or accounts.

Share This

The attributes below are required to be filled up to be able to use LDAP authentication.

• uid – User name
• userPassword – User password
• uidNumber – UID
• gidNumber – GID
• homeDirectory – Home directory
• loginShell – Login shell

If you are using Fedora Directory Server, it has a great GUI tool for managing the required Posix attributes.

Setup Authentication

1. Click System, select Administration and click Authentication. This will launch the Authentication Configuration window.

2. Check Enable LDAP Support and click the Configure LDAP button.

3. Fill in the LDAP Search Base DN and LDAP Server fields. Click Ok when you are done.

4. Click the Authentications tab and check Enable LDAP Support.

5. Click the Options tab and check Local authorization is sufficient for local users and Create home directories on the first login. Click Ok when you are done.

6. Type in getent passwd in a terminal window. You should see your Active Directory user accounts.

Finally, reboot your computer. You should now be able to login using LDAP user accounts.

If your LDAP server requires authentication or its attributes does not conform to the RFC 2307 specification, you need to edit the file /etc/ldap.conf to make this work. See Active Directory Authentication for an example.

The version of sudo that comes with RHEL/CentOS 5 does not work with non local user accounts. While this is not yet fixed, use the sudo rpm package for Fedora 8.

Share This

Creating the Virtual Mail User Account

Since the user names will be stored in MySQL, we will have to create a user that will be the owner for all the files belonging to the MySQL user names.

1. Create a new user, we will call it vmail. Change the Login Shell to /sbin/nologin, this user account should not be used for logging in. Learn how to use the User Manager application here.

2. Take note of the User ID and Home Directory of vmail.

3. Click the Groups tab and now note down the Group ID of vmail. We’ll be needing all of them later.

Configuring Postfix

1. Install a version of Postfix with MySQL support.

2. Create the file /etc/postfix/mysql-domains.cf containing the lines below.

host = localhost
user = postfix
password = your_password
dbname = postfix
table = domain
select_field = domain
where_field = domain
additional_conditions = and backupmx = '0' and active = '1'

3. Create the file /etc/postfix/mysql-users.cf containing the lines below.

host = localhost
user = postfix
password = your_password
dbname = postfix
table = mailbox
select_field = maildir
where_field = username
result_format = %sMaildir/

4. Create the file /etc/postfix/mysql-aliases.cf containing the lines below.

host = localhost
user = postfix
password = your_password
dbname = postfix
table = alias
select_field = goto
where_field = address

5. Edit the postfix configuration file /etc/postfix/main.cf and edit the line below.

mydestination = $myhostname, localhost.$mydomain, localhost

and add the lines below

virtual_mailbox_domains = mysql:/etc/postfix/mysql-domains.cf
virtual_mailbox_maps = mysql:/etc/postfix/mysql-users.cf
virtual_alias_maps = mysql:/etc/postfix/mysql-aliases.cf
virtual_mailbox_base = /home/vmail
virtual_uid_maps = static:501
virtual_gid_maps = static:501

virtual_mailbox_base, virtual_uid_maps and virtual_gid_maps should contain the home directory, user id and group id of vmail respectively.

Make sure $mydomain in mydestination has been removed, otherwise the lookup will not work and you will get a “User unknown in local recipient table” error.

6. Restart the Postfix or MailScanner service if you have installed it. Learn how to start and stop services here.

7. You should now be able to send email to addresses found in MySQL. See Test Postfix using Telnet and try using MySQL email addresses instead of the system user names.

Configuring Dovecot

1. Create the file /etc/dovecot-mysql.conf containing the lines below.

driver = mysql
connect = host=localhost dbname=postfix user=postfix password=password
default_pass_scheme = PLAIN
password_query = SELECT password FROM mailbox WHERE username = '%u'

2. Edit the file /etc/dovecot.conf and change the value of the following keys below.

passdb sql {
  args = /etc/dovecot-mysql.conf
}

userdb static {
  args = uid=501 gid=501 home=/home/vmail/%d/%n
}

uid, gid and home should contain the user id, group id and home directory respectively of the vmail user account.

Comment out all the other passdb and userdb sections except for those specified above to ensure that nothing will conflict with our LDAP virtual accounts.

3. Restart the dovecot service. Learn how to start and stop services here.

4. You should now be able to login using the user names found in MySQL. See Test Dovecot using Telnet and try using MySQL user names instead of the system user names.

If you encounter any problems, check the log file at /var/log/maillog.

Share This

Installing Postfix Admin

1. Install the Postfix Admin requirements using the command below.

yum install mysql-server php-mysql php-imap

2. Download the latest stable version of Postfix Admin in .tar.gz format here. Assuming you got the file postfixadmin-2.2.1.1.tar.gz and it is located on your Desktop, type in the commands below to extract and to put it into its proper directory.

cd /usr/share
tar -xvzf ~/Desktop/postfixadmin-2.2.1.1.tar.gz
mv postfixadmin-2.2.1.1 postfixadmin

The PostfixAdmin archive has to be extracted directly into the /usr/share directory to enable Linux to apply the proper SELinux Context into the files.

3. Edit the file /usr/share/postfixadmin/config.inc.php and update the following lines below.

$CONF['configured'] = true;
$CONF['postfix_admin_url'] = '/postfixadmin';
$CONF['database_type'] = 'mysqli';
$CONF['database_host'] = 'localhost';
$CONF['database_user'] = 'postfix';
$CONF['database_password'] = 'your_password';
$CONF['database_name'] = 'postfix';
$CONF['domain_path'] = 'YES';
$CONF['domain_in_mailbox'] = 'NO';
$CONF['encrypt'] = 'cleartext';
$CONF['emailcheck_resolve_domain] = 'NO';

Creating the Postfix Admin Database

1. Start the mysqld service. Learn how to start and stop services here.

2. Create the Postfix Admin MySQL database using the commands below. The default root password of MySQL is a blank password.

mysql -u root -p -e "CREATE DATABASE postfix;"
mysql -u root -p -e "CREATE USER postfix IDENTIFIED BY 'password';"
mysql -u root -p -e "GRANT ALL PRIVILEGES ON postfix.* TO postfix;" 

Configuring the Postfix Admin Web Application

1. Create the file /etc/httpd/conf.d/postfixadmin.conf containing the line below.

Alias /postfixadmin /usr/share/postfixadmin

2. Start the httpd service. Learn how to start and stop services here.

3. Go to the Postfix Admin setup page at http://localhost/postfixadmin/setup.php and create a new admin user. The admin user name should be a valid email address. Delete setup.php when you are done.

4. Go to the Postfix Admin login page at http://localhost/postfixadmin/ and login using your newly created admin account.

5. Congratulations, it works.

Share This

• Has graphical tools to manage users, groups, and server configurations
• Supports Active Directory synchronization
• Supports multi-master replication
• Supports secure authentication and communication
• Supports LDAP version 3
• LDAP based update of schema, configurations, and access control information

This article describes how to install and use the Fedora Directory Server.

How to install Linux

You can use either Red Hat Enterprise Linux 5 or CentOS 5. RHEL 5 can be purchased from Red Hat and comes with support. CentOS 5 on the other hand can be downloaded here.

1. How to install CentOS 5.

2. How to setup CentOS 5.

How to install and configure the Fedora Directory Server

This section is about installing Fedora Directory Server and using its graphical management tool.

1. How to setup the Fedora Directory Server.

2. How to use the Fedora Management Console.

3. How to configure Fedora Directory Server plug-ins.

Synchronizing with Active Directory

This section describes how to synchronize with Active Directory. With this feature, you can reduce your Windows Server license requirements for your LDAP applications.

1. How to synchronize with Active Directory.

2. How to install SSL certificate in Fedora Directory Server. This is needed to replicate password changes in FDS to Active Directory.

3. How to replicate Active Directory password changes to Fedora Directory Server.

Active Directory synchronization is not yet perfect. Here are some issues you need to be aware of when synchronizing with Active Directory.

Share This

Users

The Last Name is required in Fedora Directory Server so make sure all users have it in Active Directory.

User Passwords

The Active Directory user passwords can only be replicated to FDS by installing the PassSync utility to capture password changes before they are stored in a hashed format. This is the only way to get the user’s password from Active Directory.

The PassSync utility does not work in the 64 bit versions of Windows Server. It also stores the passwords used to authenticate with FDS and the certificate database unencrypted in the registry.

Organizational Units

Organizational Units, like Accounting, Domain Controllers, Engineering and Sales and Marketing in the screen shot, are not automatically synchronized. Every time you create a new one in Active Directory, you need to manually create the same in Fedora Directory Server to synchronize its contents.

Containers

Containers, like Computers, ForeignSecurityPrincipals, and Users in the screen shot, is similar to the Organizational Unit but uses a different distinguished name.

It uses CN=name instead of OU=name for its relative distinguished name.

To create an organizational unit with the same naming convention, you have to extend the FDS schema.

You can use the setupusers.sh script to create the Users organizational unit for you. Just type in ./setupusers.sh “dc=acme,dc=local” to automatically create the Users container in FDS. Replace “dc=acme,dc=local” with your own base DN.

Share This

Launching the Fedora Management Console

The Fedora Management Console requires the Java Runtime Environment from Sun Microsystem.

1. From a terminal window, type in fedora-idm-console. This will launch the Fedora Console Login window.

 

User ID

cn=directory manager

Password

the directory manager password

Administration URL

localhost:9830

 

The values above assumes you have used the default values.

2. Click the + sign corresponding to your server. Next, click the + sign corresponding to Server Group and click Directory Server. Finally, click the Open button in the Directory Server page.

3. Click the Configuration tab.

Configuring Fedora Directory Server Plug-ins

1. Click the + sign corressponding to Plug-ins.

2. Click the Distributed Numeric Assignment Plugin.

3. Check Enable plug-in and click the Save button.

4. Click Ok.

5. Restart the dirsrv service. Learn how to stop and start services here.

Share This

Launching the Fedora Management Console

The Fedora Management Console requires the Java Runtime Environment from Sun Microsystem.

1. From a terminal window, type in fedora-idm-console. This will launch the Fedora Console Login window.

 

User ID

cn=directory manager

Password

the directory manager password

Administration URL

localhost:9830

 

The values above assumes you have used the default values.

2. Click the + sign corresponding to your server. Next, click the + sign corresponding to Server Group and click Directory Server. Finally, click the Open button in the Directory Server page.

3. Click the Directory tab.

4. Click the folder corresponding to your domain.

Creating a New User

A User is an object used to store user information and authentication information.

1. Right click your domain, select New and click User.

2. In the Create New User window, fill in the user information and click Ok when you are done.

Creating a New Group

A Group is a container used to logically organize users into an easily identifiable structure.

1. Right click your domain, select New and click Group.

2. In the Create New User window, fill in the group information.

3. Add the member users in the Members section. Click Ok when you are done.

Creating a New Organizational Group

An organizational unit is an administrative-level container that is used to logically organize objects. You can create objects into an Organization Unit or copy and paste an existing object into it.

1. Right click your domain, select New and click Organizational Unit.

2. In the Create New Organizational Unit window, fill in the organizational unit information and click Ok when you are done.

Related Pages

How to configure plug-ins in Fedora Directory Server

Share This