appbaseio / appbaseio/reactivesearch-api

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

未關閉
#367 0 則留言 0 個 reaction 已指派 1 人 已被 @deepjyoti30 認領 在 GitHub 檢視
主要語言
Go
星號
212
分支
29
PR 合併指標
30 天內沒有已合併 PR

描述

### 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](https://github.com/appbaseio/reactivesearch-api/blob/9fa9ea572f3fc50399c9e575bcedd4735a2a36d7/plugins/permissions/handlers.go#L45) 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](https://github.com/appbaseio/reactivesearch-api/blob/9fa9ea572f3fc50399c9e575bcedd4735a2a36d7/plugins/auth/middleware.go#L213) 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](https://github.com/appbaseio/reactivesearch-api/blob/9fa9ea572f3fc50399c9e575bcedd4735a2a36d7/plugins/auth/middleware.go#L245) 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?

貢獻指南

這個儲存庫沒有索引到貢獻指南

評估

這個 Issue 還沒有評估資料。

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

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