MokoConsulting/MokoGitea-APP
1
0
Fork 0
Code Issues 158 Pull Requests 3 Releases 96 Wiki Activity

feat: organization-level 2FA requirement for members #208

New Issue
Closed
opened 2026-05-26 16:38:56 +00:00 by jmiller · 1 comment
jmiller commented 2026-05-26 16:38:56 +00:00
Owner
Copy Link
Copy Source

Summary

Allow organization owners to require all members to have 2FA enabled. Members without 2FA configured would be prompted to set it up before accessing org resources.

Requirements

  • Org setting: Require 2FA for all members
  • Enforcement: block access to org repos/teams until 2FA is configured
  • Grace period option (e.g. 7 days to set up)
  • Admin notification of non-compliant members
  • API support for the setting

Authored-by: Claude Opus 4.6 (1M context) noreply@anthropic.com

## Summary Allow organization owners to require all members to have 2FA enabled. Members without 2FA configured would be prompted to set it up before accessing org resources. ## Requirements - [ ] Org setting: Require 2FA for all members - [ ] Enforcement: block access to org repos/teams until 2FA is configured - [ ] Grace period option (e.g. 7 days to set up) - [ ] Admin notification of non-compliant members - [ ] API support for the setting --- *Authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>*
jmiller commented 2026-05-26 18:50:32 +00:00
Author
Owner
Copy Link
Copy Source

Fixed in dev, tested. Deploying to production in v05.05.00.

Authored-by: Claude Opus 4.6 (1M context) noreply@anthropic.com

Fixed in dev, tested. Deploying to production in v05.05.00. *Authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>*
Sign in to join this conversation.
Labels
Clear labels
breaking-change
Breaking API or behavior change
 ci-cd
CI/CD pipeline changes
 config
Configuration changes
 dependencies
Dependency updates
 deploy-failure
Deployment failed
 docker
Docker/container changes
 documentation
Documentation changes
 good first issue
Good for newcomers
 health-check
Repo health check result
 help wanted
Extra attention needed
 mokostandards
Related to MokoStandards framework
 push-failure
Git push operation failed
 security
Security vulnerability or hardening
 size/l
200-500 lines changed
 size/m
50-200 lines changed
 size/s
10-50 lines changed
 size/xl
500+ lines changed
 size/xs
< 10 lines changed
 standards-drift
Deviates from MokoStandards
 standards-update
MokoStandards compliance update
 sync-failure
Sync or mirror failed
 tech-debt
Technical debt and TODO/FIXME items
 upstream
upstream
Inherited from upstream Gitea
 work-in-progress
Draft or incomplete work
No labels
Priority Medium
Type Feature
Milestone
No items
No Milestone
Assignees
Clear assignees
jmiller (Jonathan Miller) moko-deploy (Moko Deploy Bot)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoGitea-APP#208
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?