lunny/helm-chart
1
0
Fork 0
Code Issues 36 Pull Requests 14 Actions Packages Projects Releases 93 Wiki Activity

Option to disable Query Auth Token #609

New Issue
Closed
opened 2024-01-27 01:36:19 +00:00 by buzzsurfr · 1 comment
buzzsurfr commented 2024-01-27 01:36:19 +00:00 (Migrated from gitea.com)
Copy Link

I'm getting the following warning whenever I'm running a CLI command:

2024/01/27 00:48:24 .../setting/security.go:168:loadSecurityFrom() [W] Enabling Query API Auth tokens is not recommended. DISABLE_QUERY_AUTH_TOKEN will default to true in gitea 1.23 and will be removed in gitea 1.24.

The Configuration Cheat Sheet covers how to set the flag.

DISABLE_QUERY_AUTH_TOKEN: false: Reject API tokens sent in URL query string (Accept Header-based API tokens only). This setting will default to true in Gitea 1.23 and be deprecated in Gitea 1.24.

However, there's no way in the helm template to set this configuration. (Is there?)

Feature request is to add this as an option to the helm chart. I can provide if needed.

I'm getting the following warning whenever I'm running a CLI command: ``` 2024/01/27 00:48:24 .../setting/security.go:168:loadSecurityFrom() [W] Enabling Query API Auth tokens is not recommended. DISABLE_QUERY_AUTH_TOKEN will default to true in gitea 1.23 and will be removed in gitea 1.24. ``` The [Configuration Cheat Sheet](https://docs.gitea.com/administration/config-cheat-sheet#security-security) covers how to set the flag. > `DISABLE_QUERY_AUTH_TOKEN`: false: Reject API tokens sent in URL query string (Accept Header-based API tokens only). This setting will default to true in Gitea 1.23 and be deprecated in Gitea 1.24. However, there's no way in the helm template to set this configuration. (Is there?) Feature request is to add this as an option to the helm chart. I can provide if needed.
buzzsurfr commented 2024-01-27 05:14:24 +00:00 (Migrated from gitea.com)
Copy Link

Found my issue. Per the helm chart's instructions (RTFM), I changed my values.yaml to include:

gitea:
  config:
    security:
      DISABLE_QUERY_AUTH_TOKEN: true
Found my issue. Per the [helm chart's instructions](https://gitea.com/buzzsurfr/helm-chart/src/branch/main#configuration) (RTFM), I changed my values.yaml to include: ```yaml gitea: config: security: DISABLE_QUERY_AUTH_TOKEN: true ```
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
has/backport
in progress
invalid
kind/breaking
kind/bug
kind/build
kind/dependency
kind/deployment
kind/docs
kind/enhancement
kind/feature
kind/lint
kind/proposal
kind/question
kind/refactor
kind/security
kind/testing
kind/translation
kind/ui
need/backport
priority/critical
priority/low
priority/maybe
priority/medium
reviewed/duplicate
reviewed/invalid
reviewed/wontfix
skip-changelog
status/blocked
status/needs-feedback
status/needs-reviews
status/wip
upstream/gitea
upstream/other
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: lunny/helm-chart#609
No description provided.
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?