sred-urv / moodle-auth_ip Goto Github PK

Hi,

Instead of checking if any user is login in through allowed IPs, Is there a way we can map a specific user to particular ip ?

From an email:

We would like to use the Authentication plugin restricted by IP. We use Moodle 4.1.

I have the following question:
Is the plugin Authentication by IP working well with IPv6 addresses and domains?

If so, what is the acceptable format?

For example :

2b00:1110:217:d962:0:33:e35e:1f00 - this format seems to be working
2b00:1110:217:d962:0:33:e35e::/96 - not working
2b00:1110:217:d962:0:33:e35e:0000 - not working
2b00:1110:217:d962:0000:0033:e35e:0000/96 - not working

Thank you,
Judit Gyulai

ie the use case if that we don't want to actually authenticate via this plugin, but via some other existing plugin like ldap or saml which don't have an internal password. So we'd configure this plugin to be earlier in the plugin priority list, and then have a new config checkbox something like 'Don't authenticate, just prevent login unless in ip whitelist'

• add settings for 'also check IP before logging in', along with a configurable fail message
• If this setting is true then the existing ip logic would be implemented in the pre_loginpage_hook and loginpage_hook, if they fail they get a nice configurable error message.
• have tokens in the error message to clearly help the user see why it failed and what their own ip address is
• MAYBE? If set the user_login() would always return false too. test how this works with the saml2 auth and see how the two pre_auth hooks clash or not
• have a way to logout anyone currently logged in who's ip address doesn't match

Hi, we're having a problem with our moodle site (v3.4.2 Build: 20180319) and using the Auth by IP plugin.

When we bulk upload users with authentication set to IP and their password specified in the bulk upload file the user is unable to login. When authentication is changed to manual, the password set in the file and the bulk upload repeated the users are able to login correctly. If we then try to bulk change the authentication method back to IP the user is now unable to login again.

If a user is created manually, a password assigned and authentication set to IP then they are able to login as expected, the issue only occurs to users created or updated via the bulk upload process.

Any assistance greatly appreciated

Thanks