when clicking on install button , it is throwing this error

An error occurred
The plugin Login is not enabled. You can activate the plugin on Settings > Plugins page in Matomo.

Could you enable the plugin?

@mattab @tsteur I hit this issue today. Here's more information:

1. Login as super user
2. Enable matomo LDAP plugin - https://plugins.matomo.org/LoginLdap
3. Clear the session objects on server and relogin as super user.
4. Go to marketplace and try to install a plugin . It fails with The plugin Login is not enabled. You can activate the plugin on Settings > Plugins page in Matomo.

From what I can make out:

1. When LDAP plugin is enabled, the Login plugin is disabled. The super user can still login
2. When you install a plugin now from the marketplace, the installer redirects to a page where it asks for the password for confirmation. This is handled by the Login module (per the url bar which says &module=Login iirc) which is now disabled and thus the error message.

To hit the problem, it is important that you had not entered the password previously! I guess this is because it's remembered in the session somewhere. This is why step 3 above is important.

Workaround: If using the LDAP module, the super user has to disable it first and then install modules and then re-activate the LDAP module.

Can this bug be re-opened? Maybe a doc fix or a code fix.

I dont think to disable and enable LDAP every time you want to install something is a viable solution...

@mattab : This issue is still open, is there any intention to fix this?

@cronventis are you using the latest version of Matomo and also the latest version of the other plugins?

Yes, and yes.

Matomo 4.3.1
Ldap: 4.3.0

AFAIK this should have been fixed by #15945 and I just tried to reproduce this but couldn't. Is this still the same error that is happening? What's the URL when this error happens?

Hmmmm... Just now I tried it again to get the url and error message....... But its working now? wt*?

@cronventis Thanks for the confirmation that it's working now. I'm closing this one then. If you experience this or another issue again, feel free to create a new issue here.