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

User login does not work after changing Authentication Source without BIND password #2669

New Issue
Open
opened 2025-11-02 04:43:58 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-02 04:43:58 -06:00
Owner
Copy Link

Originally created by @joga252 on GitHub (Dec 18, 2018).

  • Gitea version (or commit ref): 1.6.1
  • Git version: 2.20.0 64 bit for Windows
  • Operating system: Windows Server 2016
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL Express
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

After deactivating Enable User Synchronization in Administration area and saving changes without providing the Bind Password for the LDAP connection (see the blue boxes), user login is no more possible. Saving again with provided password re-enables users to login to the website.

Screenshots

image

Originally created by @joga252 on GitHub (Dec 18, 2018). - Gitea version (or commit ref): 1.6.1 - Git version: 2.20.0 64 bit for Windows - Operating system: Windows Server 2016 - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [x] MSSQL Express - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ## Description After deactivating *Enable User Synchronization* in Administration area and saving changes without providing the *Bind Password* for the LDAP connection (see the blue boxes), user login is no more possible. Saving again with provided password re-enables users to login to the website. ## Screenshots ![image](https://user-images.githubusercontent.com/1165349/50161085-17173100-02db-11e9-91d3-381f7ee2848f.png)
GiteaMirror added the issue/confirmedtype/bug labels 2025-11-02 04:43:58 -06:00
GiteaMirror commented 2025-11-02 04:43:59 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Dec 23, 2018):

Bind password is needed for this auth source to work if your server does not allow anonymous connections

@lafriks commented on GitHub (Dec 23, 2018): Bind password is needed for this auth source to work if your server does not allow anonymous connections
GiteaMirror commented 2025-11-02 04:43:59 -06:00
Author
Owner
Copy Link

@c-key commented on GitHub (Dec 28, 2018):

The Problem is that on every change on the site the "Bind Password" must be refilled. If the field is blank and for example the option "Enable User Synchronization" will be deactivated this auth source doesn't work. After refill the password and save the site without any modification the auth source will work as normal.
Is it a security feature that the bind password must be refilled on every change on the site or is this a bug?

@c-key commented on GitHub (Dec 28, 2018): The Problem is that on every change on the site the "Bind Password" must be refilled. If the field is blank and for example the option "Enable User Synchronization" will be deactivated this auth source doesn't work. After refill the password and save the site without any modification the auth source will work as normal. Is it a security feature that the bind password must be refilled on every change on the site or is this a bug?
GiteaMirror commented 2025-11-02 04:44:00 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Jan 23, 2019):

yes bind password if it was set should be shown here

@lafriks commented on GitHub (Jan 23, 2019): yes bind password if it was set should be shown here
GiteaMirror commented 2025-11-02 04:44:00 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Mar 24, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Mar 24, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
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 issue/confirmed 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#2669
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?