github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

'ENABLE_BASIC_AUTHENTICATION: false" doesn't block login from browser if a password is set for an OpenID Connect (Entra ID) #13248

New Issue
Closed
opened 2025-11-02 10:36:11 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-02 10:36:11 -06:00
Owner
Copy Link

Originally created by @flotpg on GitHub (Jul 5, 2024).

Description

Hi,
I've setup a fresh instance which uses OpenID Connect via Entra ID / Azure Active Directory.
I noticed that a user who logged in via OpenID Connect is still able to set a password under /user/settings/account:
CleanShot 2024-07-05 at 21 50 46@2x

So I tried pushing to the repo using that manually set password which works and I thought it's a good idea to check, If we can disable this.

The only thing I found is this: https://docs.gitea.com/administration/config-cheat-sheet#service-service

[service]
ENABLE_BASIC_AUTHENTICATION: false

It somehow works - I can't git push anymore using that password but it doesn't block login from browser so the user can login using that manually set password which renders all security policies we provide by our IDP useless :)

CleanShot 2024-07-05 at 21 53 24@2x

How can I disable password login completely or better prevent openID users, to change or manually set a password?

Many thanks and best regards, Flo.

Gitea Version

1.22.1

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

Ubuntu 22.04

How are you running Gitea?

binary

Database

MySQL/MariaDB

Originally created by @flotpg on GitHub (Jul 5, 2024). ### Description Hi, I've setup a fresh instance which uses OpenID Connect via Entra ID / Azure Active Directory. I noticed that a user who logged in via OpenID Connect is still able to set a password under /user/settings/account: ![CleanShot 2024-07-05 at 21 50 46@2x](https://github.com/go-gitea/gitea/assets/20798074/0d2ac5e5-e3fd-49c4-9f48-e95617757caa) So I tried pushing to the repo using that manually set password which works and I thought it's a good idea to check, If we can disable this. The only thing I found is this: https://docs.gitea.com/administration/config-cheat-sheet#service-service ``` [service] ENABLE_BASIC_AUTHENTICATION: false ``` It somehow works - I can't git push anymore using that password but it doesn't block login from browser so the user can login using that manually set password which renders all security policies we provide by our IDP useless :) ![CleanShot 2024-07-05 at 21 53 24@2x](https://github.com/go-gitea/gitea/assets/20798074/367e25c9-898d-4605-b15f-c15ae3769631) How can I disable password login completely or better prevent openID users, to change or manually set a password? Many thanks and best regards, Flo. ### Gitea Version 1.22.1 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System Ubuntu 22.04 ### How are you running Gitea? binary ### Database MySQL/MariaDB
GiteaMirror added the type/bug label 2025-11-02 10:36:11 -06:00
GiteaMirror commented 2025-11-02 10:36:13 -06:00
Author
Owner
Copy Link

@charles7668 commented on GitHub (Jul 6, 2024):

Maybe related to #31535.

@charles7668 commented on GitHub (Jul 6, 2024): Maybe related to #31535.
GiteaMirror commented 2025-11-02 10:36:13 -06:00
Author
Owner
Copy Link

@kdumontnu commented on GitHub (Jul 6, 2024):

Maybe related to #31535.

Yes, I believe the PR you linked is intending to solve this issue and a step towards better SSO IDP management

@kdumontnu commented on GitHub (Jul 6, 2024): > Maybe related to #31535. Yes, I believe the PR you linked is intending to solve this issue and a step towards better [SSO IDP management ](https://github.com/go-gitea/gitea/issues/23794)
GiteaMirror commented 2025-11-02 10:36:13 -06:00
Author
Owner
Copy Link

@kdumontnu commented on GitHub (Jul 9, 2024):

Closed with https://github.com/go-gitea/gitea/pull/31535

(also potential dupe of https://github.com/go-gitea/gitea/issues/13606)

@kdumontnu commented on GitHub (Jul 9, 2024): Closed with https://github.com/go-gitea/gitea/pull/31535 (also potential dupe of https://github.com/go-gitea/gitea/issues/13606)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#13248
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?