Hello app maintainers,
we made some changes to the Nextcloud 2FA logic that requires 2FA providers to populate their enabled/disabled state to the Nextcloud server, a.k.a making 2FA providers stateful. Before this change, the Nextcloud server used to load all provider apps and ask them if they are enabled for a given user. Since this doesn't work when an app is (temporarily) disabled or fails to load, we now use a registry that persists this state. In addition to a small performance improvement, this will allow us to enhance the 2FA mechanism for Nextcloud 15.
Please see the server changes at nextcloud/server#9632 and update your app so that it registers the provider's state on the IRegistry whenever it changes.
As a reference implementation, you might find it helpful to check out the following apps which have been updated for this breaking change:
Let me know if you need more info about the required changes 😉
Thanks for developing a 2FA provider for Nextcloud 🚀 ☁️ 🔐
Hello app maintainers,
we made some changes to the Nextcloud 2FA logic that requires 2FA providers to populate their enabled/disabled state to the Nextcloud server, a.k.a making 2FA providers stateful. Before this change, the Nextcloud server used to load all provider apps and ask them if they are enabled for a given user. Since this doesn't work when an app is (temporarily) disabled or fails to load, we now use a registry that persists this state. In addition to a small performance improvement, this will allow us to enhance the 2FA mechanism for Nextcloud 15.
Please see the server changes at nextcloud/server#9632 and update your app so that it registers the provider's state on the
IRegistrywhenever it changes.As a reference implementation, you might find it helpful to check out the following apps which have been updated for this breaking change:
Let me know if you need more info about the required changes 😉
Thanks for developing a 2FA provider for Nextcloud 🚀 ☁️ 🔐