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…

[imagem] 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

Acesso Inválido usando Chave Global em Todos os usuários

Dev

JustinBack (Justin René Back) Novembro 29, 2020, 6:52pm 3

Ah, certo, isso mudou recentemente? Pois eu tinha em mente que o cabeçalho era Api-User.

Tópico		Respostas	Visualizações
Generate/Regenerate api_key for a user API not working Development rest-api	4	1004	6 de Dezembro de 2019
Issues using API with long-established/working key Support	2	430	20 de Abril de 2022
Unable to edit topic via API despite topic write access Bug rest-api	4	798	4 de Março de 2022
Newly enforced api_username restriction? Development rest-api	4	642	29 de Outubro de 2020
404 when trying to create an API key for system user Bug	3	1368	11 de Agosto de 2020

Acesso Inválido usando Chave Global em Todos os usuários

Tópicos relacionados