/meetings API - The server understood the request, but refused to...

[Jeff Marshall]

"message": "The server understood the request, but refused to fulfill it because the access token is missing required scopes or the user is missing required roles or licenses.",
"errors": [
{
"description": "The server understood the request, but refused to fulfill it because the access token is missing required scopes or the user is missing required roles or licenses."
}
],
"trackingId": "ROUTER_62431B41-9C3C-01BB-1348-0AFE38171348"

Above is the response I am getting from /v1/meetings (GET method) with valid access token. Anyone can help me in identifying the root cause?. I am having spark:all permission enabled in my app integration.

[Cheryl-Powers]

Hello. I have developed an Integration using the Webex Developer tool and then created the VLS configuration in our SuccessFactors LMS. Our integration and VLS configuration needs to be utilized by hundreds of instructors teaching virtually. Currently, the only instructor that can schedule a VLS class choosing the VLS configuration we created, is the "owner" of the integration itself. All other instructors receive a WebexRest 403 Forbidden error message as if they don't have the permissions/credentials on the server. When we create an instructor, adding VLS capabilities, we have to add their email address because that is the username they use in Webex. All webex users have host meeting capabilities and don't have to be designated as a virtual instructor with a virtual class.

Even when we add the other instructors to the VLS settings tab in SuccessFactors LMS with their email address, they aren't able to access the VLS server. I have internal webex support only, who aren't familiar with how the integration should work within our LMS. I can't get any support from SAP at all. I would be very appreciative if you would share your experience on how to get our Webex integration to apply to all instructors. The SAP document said none of the instructors needed to provide a password, yet, the integration that resides in "my-apps" on the webex site, seems to be prohibited for other instructors. Only the creator of the integration can do what is supposed to do, but that would not be practical. We can't have hundreds of instructors creating their own integration. There must be something else we missed. Our internal webex support said we didn't need admin rights and we tried testing that, without success. 

Thank you so much in advance for any insight. Truly appreciate it. -Cheryl

[prashant-chinchkar]

@Jeff Marshall ,
I have User with admin role.
Also, I have integration with a meeting related scopes selected. Still I am facing same issue.
Below is the screenshot for created integration.

I also tried to get access token again with meeting related scopes, where I received below response  which doesn't include meeting scopes.

{

"access_token": "****************",

"expires_in": 1209599,

"refresh_token": "***********",

"refresh_token_expires_in": 7767565,

"token_type": "Bearer",

"scope": "identity:groups_rw spark:all spark:kms identity:groups_read spark-admin:people_write spark-admin:roles_read identity:tokens_write identity:people_read identity:tokens_read identity:people_rw spark-admin:people_read"

}

Could you please advice?
Thanks

[Jeff Marshall]

Sounds like maybe whatever user you're using to authorize with the integration doesn't have a meeting host license. The scopes in your screenshot are user/host level scopes and require that the user have a host license. For an admin there are admin specific scopes, such as meeting:admin_schedule_read. You can see what scopes work which which roles on https://developer.webex.com/docs/meetings#scopes-and-user-roles.

[Jeff Marshall]

The /meetings API requires specific scopes that are no included with the spark:all scope. You will need to ensure that your integration has the appropriate meeting related scopes selected. Additionally, the user making the API request has to have a meeting license and have a host or admin role.