I have changed nothing. All of a sudden all of my api calls are getting the api error: “You are not permitted to view the requested resource”. I even renewed my api keys and I have set the api users to have maximum privileges. Why is this happening all of a sudden??

[image]Discourse REST API Documentation :warning: Deprecation Warning! On April 6th, 2020 we dropped support for all non-HTTP header based authentication (excluding some rss, mail-receiver, and ics routes). This means that API requests that have an api_key and api_username in the query params or in the HTTP body of the request will soon stop working. Please see the example cURL request below for how to update your API requests to use the HTTP headers for authentication. Are you using HTTP Headers for the API key?

Yes, I just saw this. So this will even affect a discourse instance I host myself and haven’t updated?

What exact version you are running?

I’ve since updated. I don’t have the old version number. It was almost a year old. But the errors started occurring before I updated.

Something is fishy if this somehow affected my self hosted non-updated instance.

Without more details, including those version numbers, it’s almost impossible to say.

It should be easy to say if you do something that would make a supposedly entirely standalone self hosted instance stop working due to some unknown integration with external services.

There is nothing that should affect a standalone self-hosted install like this that hasn’t been upgraded. Even if we backported a change to an older version, you wouldn’t receive it unless you manually updated your install. Discourse out of the box doesn’t come with any external services unless you set them up yourself, like email and google analytics.

I didn’t update anything and started getting 403 errors on all api calls. The only thing that fixed the errors was upgrading to the new version and changing request parameters to headers. Something is causing old versions to break due to the api changes even when they are standalone, self hosted and not being explicitly updated.

[image] depeters: Something is causing old versions to break due to the api changes even when they are standalone, self hosted and not being explicitly updated. Change doesn’t occur without change. Something somewhere changed, whether you were aware of that change or not. If not in your container, then on one of the components outside it, or one of the connected systems. This is all a lot of hand-waving without something tangible to look at though.

All API calls now getting "You are not permitted to view the requested resource"

Product Support

Falco (Falco) April 11, 2020, 3:26am 2

Are you using HTTP Headers for the API key?

Topic		Replies	Views
Discourse API - Unable to query certain endpoints Product Support	7	1663	October 1, 2019
API endpoint users/by-external/ failing with authorization headers, works without Bug rest-api	2	675	June 26, 2023
Discourse_theme CLI for unsupported Discourse versions Product Support unsupported-install	6	757	November 27, 2019
WP Discourse plug in being odd WordPress	15	2507	December 6, 2019
There was an error returning the category list from Discourse Product Support wordpress	3	620	May 19, 2023

All API calls now getting "You are not permitted to view the requested resource"

Related topics