Description
I am working on updating our authentication from JWT to OAuth. I followed the instructions to create a Server-to-Server OAuth app, noting the account ID, client key, and client secret. Now I am attempting to do some test calls in Postman, to the meetings API.
I can successfully pull a Bearer Token, but when I then use it to make the call, the endpoint returns:
"code": 124,
"message": "This API does not support client credentials for authorization."
Error?
ācodeā: 124,
āmessageā: āThis API does not support client credentials for authorization.ā
How To Reproduce
1.) Create Server-to-Server OAuth application.
2.) Note account ID, client key, and client secret
3.) Set up Postman for OAuth 2.0 authentication, and get new access token
4.) Use that token for a call to the endpoint.
5.) Error is returned.
In Postman, how should I enter this in their OAuth authentication flow? Iāve been trying to do a custom call to /oauth/token, but I canāt get it to work. I get a 405 error.
To be more specific, I had a GET call to /oauth/token, with account_credentials for grant type and account ID specified, plus a Base64 representation of client key and secret (both as an Authorization header and body). Iām unable to get that to work.
Iām trying to prototype and validate in Postman before I start moving this into my production codebase. I appreciate your help and support.
Hi I also got the same error . I have a member account . I used the client credentials that admin gave. after taking the token I cant get MeetingDetails. what is the reason. Here is my code,
import requests as rq
import base64
import json
cID=āā¦ā
cSec=āā¦ā
userID=āā¦ā
#credential_ID:credential_Secret
credentials= f"{cID}:{cSec}" #encode for base =64
bStream= credentials.encode(āasciiā) #bit stream
encode64= base64.b64encode(bStream)
sEncode= encode64.decode(āasciiā)
my error : "resulted in a 401 Unauthorized response: {ācodeā:124,āmessageā:āThis API does not support client credentials for authorization.ā} "
I canāt download my meeting recordings.
I have a JWT app that has been doing this for 2 years but it will be deprecated in June 2023.
I tried to create an OAuth app but I canāt whitelist a domain because students need to be able to enter the Zoom meeting as soon as the host starts the room and the students donāt all have the same domain.
I intend to purchase a Pro Plan subscription for my Zoom account to manage and create Zoom meetings for my company.
I have a query regarding the creation of licensed users for my Zoom Pro account. After the purchase of the Pro plan, is it necessary to make additional payments for creating licensed users, or can I create licensed users for free within the Pro plan?
Upon attempting to add a new licensed user, I received the following error message:
{
ācodeā: 3412,
āmessageā: āYour request to add a new Licensed user could not be approved at this time because your account has reached the permitted maximum number of 1 paying users. Please purchase additional licenses or contact the Zoom support team to provision additional users in your account.ā
}
Could you please provide clarification on whether additional payments are required for creating licensed users within the Pro plan?
@devang.wappnet You can create upto 9999 basic users (free plan users) in your account with a Pro Account, however if you want to create a licensed users (for ex: create meetings that dont have a 40 minute limit), then you need to pay for the license of the user.
I am experiencing this same issue when using a Server-to-Server authentication token.
C# class that first does a POST to the https://zoom.us/oauth/token url using form url encoded values for grant_type and account_id (per the developer docs) with Base64 endoded clientId:clientSecret. This returns the access_token (Bearer) successfully.
However, when I make a subsequent request using the standard .net6 http client with an Authorization header set to āBearer ${access_token}ā the subsequent GET requests (such as https://api.zoom.us/v2/users?page_size=100&page_number=1) fail with the āAPI does not support client credentials for authorizationā error.
What is strange to me is that I can make the IDENTICAL requests in a REST client (aka Postman, but we use Insomnia) to get the access token and then use that token in other requests and the requests succeed.
Iām really confused and any assistance would be greatly appreciated.