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…

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

Accesso non valido con Global Key per tutti gli utenti

Sviluppatore

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

Ah, d’accordo, è stato cambiato di recente? Perché avevo in mente che l’header fosse Api-User.

Argomento		Risposte	Visualizzazioni
Generate/Regenerate api_key for a user API not working Development rest-api	4	1005	Dicembre 6, 2019
Issues using API with long-established/working key Support	2	430	Aprile 20, 2022
Unable to edit topic via API despite topic write access Bug rest-api	4	798	Marzo 4, 2022
Newly enforced api_username restriction? Development rest-api	4	642	Ottobre 29, 2020
404 when trying to create an API key for system user Bug	3	1369	Agosto 11, 2020

Accesso non valido con Global Key per tutti gli utenti

Argomenti correlati