Setup config:
Installation of DNS:
[
]
[
]
[
]
[
]
[
]
[
]
AD CERT SERVICE INSTALLATION:
[
]
[
]
[
]
[
]
[
]
[
]
[
]
[
]
[
]
Connection test:
[
]
Linux Config:
Users for ldap:
[
]
Setting up privileges ldap:
[
]
Adding organization units:
[
]
OU CHECKS:
[
]
Adding Users into groups:
[
]
[
]
Configuring ldap to use dn for login:
[root@abc
~]# vim /etc/phpldapadmin/config.php
$servers->setValue('server','name','ABC LDAP');
$servers->setValue('server','host','127.0.0.1');
$servers->setValue('server','port',389);
$servers->setValue('server','base',array('dc=big-guy,dc=com'));
$servers->setValue('login','attr','dn');
// $servers->setValue('login','attr','dn');
[
]
Setting up IP for phpldapadmin for specific networks.
[
]
[
]
[
]
[
]
[
]
[
vi /etc/yum.repos.d/lsc-project.repo
Add content as below and save:
[lsc-project]
name=LSC project packages
baseurl=http://lsc-project.org/rpm/noarch
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-LTB-project
rpm --import http://ltb-project.org/wiki/lib/RPM-GPG-KEY-LTB-project
yum install -y lsc java
]
[
]
[
]
Exporting the Client Certs:
[
]
[
]
[
]
[
]
[Export and Test Synchronized password
Failed]
[
Conclusion:
The following requirements have been put into practise and tested in accordance with the instruction
memo.
Big-Guy Company's design of centralised access (Windows AD)
Using a Linux machine, ABC users can access Big-Guy Company (Windows AD).
Users from BigGuy can simply import their usernames to gain access to Linux systems.
and the Openldap server password ought to function.
The synchronisation function and export part is undone. The script error ought to be the cause.
Therefore, if user accounts and passwords have changed, the administrator must update them.