Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Internal Server Error when posting a permission while being authenticated with another permission

未關閉
#367 0 則留言 0 個 reaction 已指派 1 人 在 GitHub 檢視

@deepjyoti30 已經在處理了。

開始於 2023年1月23日。

評估

這個 Issue 還沒有評估資料。

描述

What version of ReactiveSearch API are you using ?

8.9.0

What issue did you run into?
  1. Create a permission (API Credentials) with a read-write access to the "permissions" category.
  2. Use the credentials of the just created permission in HTTP Basic Auth to send a POST /_permission request, trying to create another permission object.
What did you expect to see?

A created permission.

What did you see instead?

Internal server error saying "*user.User" not found in request context.

From what I was able to find in the code as a non-Go developer, looks like the user is being read from the context right here for the only purpose to check if it's admin or not, which decides the permission's default settings. And if the user not found, the error is being thrown.
Looking at the auth middleware I can see it being assigned only when the request is authenticated on behalf of a user. When you use API Credentials to authenticate the request, the permission is being assigned to the context instead.
I haven't found anywhere in the documentation that you can only create permissions when authenticated as a user. So I think it's a bug.
Would it be possible to fix it by assuming the user is not an admin if the request is authenticated with the API Credentials?

主要語言
Go
星號
212
分支
29
平均合併
13 分鐘
30 天內合併 PR
2

環境準備

  • 提供 Dockerfile 或 Docker Compose 檔案
  • 有 Pull Request 範本
  • 沒有貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

appbaseio/reactivesearch-api 的其他 Issue

查看 appbaseio/reactivesearch-api 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。