github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-11 17:46:29 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Describe LDAPS setup with self-signed certificate #7993

New Issue
Open
opened 2025-11-02 07:44:59 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-02 07:44:59 -06:00
Owner
Copy Link

Originally created by @justusbunsi on GitHub (Oct 19, 2021).

In the current documentation there is no guidance on how to handle LDAPS connections with self-signed certificates.

Originally created by @justusbunsi on GitHub (Oct 19, 2021). In the current documentation there is no guidance on how to handle LDAPS connections with self-signed certificates.
GiteaMirror added the topic/authenticationtype/docs labels 2025-11-02 07:44:59 -06:00
GiteaMirror commented 2025-11-02 07:45:05 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Oct 19, 2021):

https://github.com/go-gitea/gitea/issues/16376#issuecomment-885828441

Add your certificate to a copy of the root certs file and set the SSL_CERT_FILE environment variable to the new file.

See: https://pkg.go.dev/crypto/x509@go1.16.6#SystemCertPool

and

https://cs.opensource.google/go/go/+/refs/tags/go1.16.6:src/crypto/x509/root_linux.go

(On linux that is. On windows and mac you need to add the new RootCA to the system pool.)

Unfortunately as far as I can see if we were to provide an option to set the trusted CAs, users would have to provide a file containing all root CAs.

@zeripath commented on GitHub (Oct 19, 2021): https://github.com/go-gitea/gitea/issues/16376#issuecomment-885828441 Add your certificate to a copy of the root certs file and set the `SSL_CERT_FILE` environment variable to the new file. See: https://pkg.go.dev/crypto/x509@go1.16.6#SystemCertPool and https://cs.opensource.google/go/go/+/refs/tags/go1.16.6:src/crypto/x509/root_linux.go (On linux that is. On windows and mac you need to add the new RootCA to the system pool.) Unfortunately as far as I can see if we were to provide an option to set the trusted CAs, users would have to provide a file containing all root CAs.
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 topic/authentication type/docs
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#7993
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?