[X] This is a singlebug, not a question or a configuration/webserver/proxy issue.
[X] This is not a bug in the Nextcloud App or another client.
[X] This issue is not already reported on Github (I've searched it).
[X] Nextcloud Server and the Passwords App is up to date. See Nextcloud Apps.
[X] The browser extension is up to date. See Nextcloud Apps.
Server Information
27.1.3
Client Information
Browser and Version: Firefox 121, Chrome latest
Client OS and Version: Windows 10
Extension Version: 2.5.0
Bug description
Several of my teammates were locked on Active Directory because extension keeps trying to login with invalid credentials.
Note that:
NextCloud is obviously connected to AD
Most of us didn't change credentials, but extension for some reason required relogin and extension showed big number of notifications about inability to login
details
There are 10s or more of these:
One team member actually changed the credentials on AD but didn't update it on extension, and from that moment forward extension was locking him constantly
I guess to solve this, there needs to be some form of diminishing returns to relogin, with ultimate stop of retry. This might even be configurable.
Steps to reproduce
It happens on its own
Expected behavior
Extension should do its best not to spam AD server via NC or make this configurable as AD settings differ in that regard.
⚠️ This issue respects the following points: ⚠️
Server Information
Client Information
Browser and Version: Firefox 121, Chrome latest Client OS and Version: Windows 10 Extension Version: 2.5.0
Bug description
Several of my teammates were locked on Active Directory because extension keeps trying to login with invalid credentials.
Note that:
NextCloud is obviously connected to AD
Most of us didn't change credentials, but extension for some reason required relogin and extension showed big number of notifications about inability to login
details
There are 10s or more of these: One team member actually changed the credentials on AD but didn't update it on extension, and from that moment forward extension was locking him constantly
I guess to solve this, there needs to be some form of diminishing returns to relogin, with ultimate stop of retry. This might even be configurable.
Steps to reproduce
Expected behavior
Extension should do its best not to spam AD server via NC or make this configurable as AD settings differ in that regard.
Extension Logs
No response