topic Why is it different from the requested scope? in Webex for Developers

Why is it different from the requested scope?

proster12 — Wed, 31 May 2023 02:25:24 GMT

This is the logic to get the access token using the integrated app.

authorization url
https://webexapis.com/v1/authorize?client_id=[client_id]&response_type=code&redirect_uri=https%3A%2F%2Flocalhost%2Fapp%2Ftest%2Fcallback&scope=identity%3Atokens_read%20meeting%3Aadmin_schedule_read%20meeting%3Aadmin_schedule_write%20meeting%3Aschedules_read%20meeting%3Aschedules_write%20spark-compliance%3Amessages_write%20spark%3Aall%20spark%3Akms&state=test1234

scope is defined as follows.
spark:all
spark:kms
identity:tokens_read
meeting:schedules_write
meeting:schedules_read
meeting:admin_schedules_write
meeting:admin_schedules_read
spark-compliance:messages_write

However, the returned scope is as follows.
spark:all spark:kms identity:tokens_read

Why is it different from the requested scope?

Re: Why is it different from the requested scope?

Rudrakshi — Wed, 31 May 2023 04:07:51 GMT

Hello,

If you modify the scopes for an Integration, you will also need to re-authorize it in order to reflect the updated scopes using the updated OAuth Authorization URL. If this is not the case, please drop an email to: devsupport@webex.com mentioning the ClientID.

Hope this helps!

Re: Why is it different from the requested scope?

proster12 — Wed, 31 May 2023 04:32:36 GMT

I sent the clientid by mail.