summaryrefslogtreecommitdiffstats
path: root/apps/twofactor_backupcodes/composer/composer
Commit message (Collapse)AuthorAgeFilesLines
* Add event dispatcher to OCPChristoph Wurst2019-06-252-2/+0
| | | | Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>
* Clear backupcodes reminder if no 2FA is enabledRoeland Jago Douma2019-03-052-0/+2
| | | | | | | | | | Fixes #14125 Listen to 2FA disable event. If a provider is disabled for a user. We check if there are no more providers. If there are no more providers we Remove the backupcode reminder notification (if still present). Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
* Shorten index name of calendar changes tableJoas Schilling2018-11-141-1/+1
| | | | Signed-off-by: Joas Schilling <coding@schilljs.com>
* Add job to check users for backup code remindersRoeland Jago Douma2018-10-022-0/+4
| | | | | | | | | Now that we can enforce 2FA we also should notify users that have enabled 2FA but do not yet have backup codes generated. This adds a repair step that inserts a background job to do this. Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
* Clear notification to generate backup code once codes are generatedRoeland Jago Douma2018-10-012-0/+2
| | | | Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
* Generate backups code notification if not enable but 2fa isRoeland Jago Douma2018-10-012-0/+6
| | | | | | | | | | | | Generate a notification to generate backup codes if you enable an other 2FA provider but backup codes are not yet generated. * Add event listner * Insert background job * Background job tests and emits notification every 2 weeks * If the backup codes are generated the next run will remove the job Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
* Fix backup codes column length to fix Argon2 hash valuesChristoph Wurst2018-08-212-0/+2
| | | | Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>
* Bump autoloadersRoeland Jago Douma2018-08-101-1/+1
| | | | Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
* Fix state propragation of the backup codes providerChristoph Wurst2018-08-012-0/+8
| | | | | | | | | | | | Starting with Nextcloud 14, the server knows the enabled/disabled state of 2fa providers. While it will query that information if it's unknown (on first use), it won't notice any changes. Thus, providers have to propagate that information themselves. Ref https://github.com/nextcloud/twofactor_totp/pull/263 Ref https://github.com/nextcloud/twofactor_u2f/pull/210 Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>
* Update composerMorris Jobke2018-01-122-10/+14
| | | | Signed-off-by: Morris Jobke <hey@morrisjobke.de>
* Composer updatedRoeland Jago Douma2018-01-042-16/+12
| | | | Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
* Use proper authorative-autoloader for app autoloadersRoeland Jago Douma2017-12-141-10/+1
| | | | Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
* TwoFactorBackupCodes AutoloaderRoeland Jago Douma2017-10-247-0/+605
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-28 15:33:58 +0000