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
派生
30
平均合并
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 摘要。