Open Cerberus-Zer0 opened 6 years ago
HI @leddy86,
If you have Update user option is set to Yes, then this would happen. Try to disable it. I'll mark this issue as a bug for now.
Probably we don't want to update users if they were not created using "userkey" auth method.
I think it's actually not a bug, but a incorrect usage of the plugin in this particular case.
So you are trying to log in a user using a user name and a password to get a token, then you try to login the same user using this plugin with enabled update feature.
It seems like you should create a service user instead and get a token or generate webservice token just for generating login keys your users will be using.
So I recon it's not a bug, but we can improve the plugin by have a setting to allow users with another auth types to be logged in as well.
Hi,
I’m trying to authenticate users through our web application. So far I have been successful in authenticating a user the first time however when the user token is created and they are authenticated, Moodle changes the student’s authentication method from Manual to User key authentication.
This in turn disables the password so next time the web app tries to receive a token, it fails as the password is sent but since it’s disabled (no longer Manual) it fails to authenticate and return the token.
From the looks of it, a token is not stored and I receive Missing capabilities: auth/userkey:generatekey
However I have set Authenticated Users with the permission auth/userkey:generatekey
It is probably my lack of knowledge on how the plugin works so if you could please help me understand the process then that would help greatly.
Thanks.