My boss is paying some to write a code to do this. It will work as a module in the learning path. Not random, but enough to keep The Texas Real Estate Commission happy.
Re: Ynt: Verification of user at Random Intervals
Moodle 3.9 can not send Notifications to newly created Users
I have configured Moodle 3.9 to send messages, i used the test tool and it worked. I also tested the "Forgotten your username or password?" function it works... So it sends Emails
Now, i create users by uploading them into Moodle, I wanted Moodle to generate passwords and send instruction to the user on how login, but this has failed, how do i go about this???
Re: How to prevent account creation when authenticating just for one issuer?
Hi Osvaldo,
you need to change this line:
if (!empty($CFG->authpreventaccountcreation)) {
to this one:
if (!empty($CFG->authpreventaccountcreation) && ($issuer->get('name') !== 'my-identity-issuer-name')) {
Saludos.
Iñaki.
Re: How to prevent account creation when authenticating just for one issuer?
Re: Run Now
Hi
I have same issue in my setup. I cannot see 'Run now' button like the demo in some of the videos. Any one can help please ?
Thank you
Re: Run Now
To get the "Run now" link Path to PHP CLI must be set (under Site administration▸ Server▸ System paths).
LDAP-module cannot connect to any servers: Server: '192.X.X.X', Connection: 'Resource id #567', Bind result: ''
I have installed Moodle 3.9.2 version in a Windows 10 local machine and configured LDAP authentication and the LDAP authentication working fine. Later on I have installed Moodle 3.9.2+ version in a CentOS VM machine and configured the LDAP authentication with same setting's value provided for Windows machine but I am getting this error "LDAP-module cannot connect to any servers: Server: '192.X.X.X', Connection: 'Resource id #567', Bind result: ''
Can anyone please help me what am I missing?
Re: LDAP-module cannot connect to any servers: Server: '192.X.X.X', Connection: 'Resource id #567', Bind result: ''
Re: Run Now
Re: LDAP Sync breaks when user created on external source
Hi Emma,
I know I'm quite late to this, but I've had a look at the code, and fixing this in the general case is going to be tricky. We have three settings that affect where Moodle looks for users, both when syncing them and when the user tries to log in:
- general user contexts
- context for externally created users
- whether to search subcontexts of the previous two or not.
The root of the issue is the three of them are use together to decice where to look for, but are configured and "validated" independently. That is, when processing and storing the setting for general user contexts, we don't get a chance to see what's configured in the setting for externally created users, or the setting for type of search. This is a consquence of how admin configuration settings library works.
So that makes it tricky to detect any duplicates among general user contexts and the context for externally created users while configuring the plugin. So we need to defer that "duplicates" check until we try to use the contexts in the login or sync operation.
The second factor that complicates things further is that the "duplicates" check depends on the value of the search subcontexts setting. If set to "false", things are a little bit easier, as we can rather easily identify duplicated contexts: we just need to compare them all (case insensitively) and remove exact duplicates.
But if search subcontexts is set to "true", we need to compare if any given context from the two context-related settings is a subcontext of the others, and remove those that are subcontexts of another "higer level" context. And we would probably need to do this recursively until there are no subcontexts left, as an "ancestor" context of a given subcontext could itself be a subcontext of another "ancestor" context.
So I think it's doable, but we'd need to be very careful not to "loose" any context by accident while removing duplicates.
Saludos.
Inaki.
Re: LDAP-module cannot connect to any servers: Server: '192.X.X.X', Connection: 'Resource id #567', Bind result: ''
I have disabled the SeLinux option in the config file in /etc/selinux/config, but still get same error. see below picture

Re: Run Now
Is /usr/bin/php the correct path on your system? You should see a green check mark on the right of the field if the path is correct:
If you don't see the green check mark, try running which php at the command line which should show the correct path.
Re: LDAP-module cannot connect to any servers: Server: '192.X.X.X', Connection: 'Resource id #567', Bind result: ''
To confirm SELinux is disabled, what does the command getenforce show?
Can you telnet to 192.x.x.x server on the expected port, probably 389? This is done with the command telnet 192.x.x.x 389 (you may need to install telnet with dnf install telnet).
In Moodle is the Host URL field exactly the same on the Windows and CentOS VMs on the LDAP Server page?
Re: LDAP-module cannot connect to any servers: Server: '192.X.X.X', Connection: 'Resource id #567', Bind result: ''
Re: LDAP Sync breaks when user created on external source
Having issues with Ldap Authentication settings
Hello, I am new into moodle . I am having a serious challenge settting up my connection with my company active directory(Ldap).
1. I can connect to server but once i enter values in the Contexts it and click on test settings it returns this error
LDAP error 1 reading ou=abxxxx,dc=trxxxxxxxxx,dc=net: Operations error.
kindly help, am becoming frustrated.
Thank you
Re: Having issues with Ldap Authentication settings
I have always set a bind user. It is a good idea to create a user just for this connection. The user has to have sufficient privileges (read/write/execute etc) on the ou that your users are in.
Re: LDAP-module cannot connect to any servers: Server: '192.X.X.X', Connection: 'Resource id #567', Bind result: ''
Thanks for your help. Now my Linux vm can connect to my AD server. Can you please tell me which type of permission needed for the bind user?
Re: LDAP-module cannot connect to any servers: Server: '192.X.X.X', Connection: 'Resource id #567', Bind result: ''
Thanks for your help. Now my Linux vm can connect to my AD server. Can you please tell me which type of permission needed for the bind user in AD?