No, not always. It only shows the module which have been enabled for the php cli. Depending on the system it might be possible that a different php.ini is used by the cli than the web interface. So that this is not a reliable way to check the module availability for the web access.
Hi J-ed, I ran this script and I am able to notice Ldap module is loaded. Below is the output for ldap module from the script <?php phpinfo() ?> output. Still the “Enable” button is grayed out. Also the output of “php -m” shows “ldap”
LDAP Support => enabled
RCS Version => $Id$
Total Links => 0/unlimited
API Version => 3001
Vendor Name => OpenLDAP
Vendor Version => 20444
SASL Support => Enabled
Directive => Local Value => Master Value
ldap.max_links => Unlimited => Unlimited
Place it in a directory of your web server which can be access by a browser. E.g. if the web root is /var/www/htdocs you could create a php file in this directory and named it info.php. Next you open your web browser and enter the url to your server, like http://<your-server-fqdn>/info.php
As a result an html file should be shown.
This is the only way how you can check if a php module is correctly loaded!
You are still mixing up the php web and the php cli access. So don’t try to use the php command line interface (cli) to prove or test that the php web access has the ldap module loaded. Due to the fact that you are now getting an error message if you run the php cli, you
a) haven’t installed the required php module correctly.
b) most likely haven’t modified the correct php.ini file which is used by the php web access.
Hi J-ed, Yes you were right. When I checked I saw three versions of PHP running in the server and the Web is to access PHP7.2 but PHP 7.2’s directory didn’t have ldap.so file, where as PHP 7.0 & 5.6 had the file/module.
Now I have made Apache to point/look at PHP 7.0 by renaming php_XX.conf files of both 7.2 and 5.6 versions.
Now the “enable” button activated and am able to Integrate AD with Nextcloud.
The new challenge is I have added the existing Windows File Servers’s shared folders as external storage where all AD users were given access with set certain permissions.
After adding the same folders as external storage through SMB/CIFS how can I enforce same Windows permission when accessed using AD user login.
The Idea was to have Open Source file sharing app/tool alternative to existing windows file/folder sharing. All AD users are given access with certain permissions to shared folders. How do I enforce the same access restrictions/permissions for the same share/folder when accessed through Nextcloud as an Active Directory User.