Just noticed this issue today. Generating an api key for all users with global scopes, then updating a topic will result in an invalid_access curl --location --request PUT 'https://example.com/t/-/365.json' \ --header 'Api-User: system' \ --header 'Api-Key: ***' \ --header 'Content-Type: applicati…

[이미지] JustinBack: --header 'Api-User: system' This should be Api-Username, not Api-User This header is only used for “all user” api keys, so that’s why it worked when you scoped the key to a specific user.

Ah alright, was that changed recently? As I had in mind that the header is Api-User

모든 사용자에게 글로벌 키로 잘못된 액세스 발생

개발

JustinBack (Justin René Back) 11월 29, 2020, 6:52오후 3

아, 알겠습니다. 최근에 변경된 건가요? 헤더가 Api-User인 줄 알았거든요.

글		댓글	조회수
Generate/Regenerate api_key for a user API not working Development rest-api	4	1004	12월 6, 2019
Issues using API with long-established/working key Support	2	429	4월 20, 2022
Unable to edit topic via API despite topic write access Bug rest-api	4	797	3월 4, 2022
Newly enforced api_username restriction? Development rest-api	4	642	10월 29, 2020
404 when trying to create an API key for system user Bug	3	1368	8월 11, 2020

모든 사용자에게 글로벌 키로 잘못된 액세스 발생

Related topics