Welcome to the Kinde community.

K
A
A
A
M

Authorize API button not working in non-production environments

Hi guys. The authorize api button is not working on non-production environments (production works fine). This is a complete blocker because develop against a production enviroment.

O
M
7 comments

Hey ,

Sorry that you are experiencing this issue.

We have recently made some changes to the Kinde Management API - see here.
All existing backend applications that had authorized the Kinde Management API, before this change, still have the Kinde Management API authorized.

However, after this change, only Machine-to-machine (M2M) applications can authorize the Kinde Management API.
We made this change so we could tighten the security on the access tokens to the Kinde Management API, so the risk of a malicious person making changes to your Kinde business through the Kinde Management API is now much less.

I would suggest following this guide: https://docs.kinde.com/developer-tools/kinde-api/add-a-m2m-application-for-api-access/

If you are trying to authorize the Kinde Management API for a non-M2M Kinde application and experiencing this issue. It would be because of the change mentioned above.

I would suggest creating a M2M Kinde application and authorizing the Kinde Management API to resolve this issue.

Please let me know if you have any questions or concerns on anything I said above.
Also, please let me know if you are still experiencing any issues.

Thanks , if it’s an error on my part the system should behave like it’s an error and display some error message explaining the situation to the user. not silently fail

Also, I don’t have the manage scopes option in my management api

Attachment
image.png

I’m kinda in a deadlock here. cannot set up scopes and cannot authorize due to missing scopes. what should I do?

Hey ,

if it’s an error on my part the system should behave like it’s an error and display some error message explaining the situation to the user. not silently fail
I totally agree. I have raised this with my team. We all agree the current behaviour is not ideal.

- I will reach out you to you in a DM to resolve this issue.

Add a reply
Sign up and join the conversation on Slack
Join