Go to All Forums

APM INSIGHTS APIS: OAuth Scope associated to the OAuth Access Token is disallowed

Hello

 

using APM insights api with OAUTH tokens gives me the response

{
"error_code": 1121,
"message": "OAuth Scope associated to the OAuth Access Token is disallowed."
}

 

The Zoho-oauthtoken provided was generated out of Self Client generated Grant token with ALL scopes:

Site24x7.Account.All,Site24x7.Admin.All,Site24x7.Reports.All,Site24x7.Operations.All,Site24x7.Msp.All,Site24x7.Bu.All

 

The APIs which I have issues accessing are:

www.site24x7.com/api/apminsight/ins/H

www.site24x7.com/api/apminsight/ins/101071000000034035/H

www.site24x7.com/api/apminsight/app/H

www.site24x7.com/api/apminsight/app/application-id/H

www.site24x7.com/api/apminsight/ins/instance-id/txn/list/3/apdex/H

basically all the apis listed under categories below (from:www.site24x7.com/help/api/index.html)

 

The other APIs like current status etc ... work no problems.

I have also noticed that documentation for the apis I have mentioned, does not include oauthscope : Site24x7.XXX.XXX documentation. Why is that?

 

Please advise ?

Like (2) Reply
Replies (4)

Further observation (${MYBUID} is set to valid zaaid)
Curl randomly returns internal error or OAuth scope errors.

curl -H "Authorization:Zoho-oauthtoken 1000.XYZ" -H "Cookie:zaaid=${MYBUID}" "www.site24x7.com/api/apminsight/app/H"

HTTP 400

{"error_code":1000,"message":"Internal error."}

curl -H "Authorization:Zoho-oauthtoken 1000.XYZ" -H "Cookie:zaaid=${MYBUID}" "www.site24x7.com/api/apminsight/app/H"

HTTP 401

{"error_code":1121,"message":"OAuth Scope associated to the OAuth Access Token is disallowed."}

 

Please advise, as this is topping us from evaluating integration capabilities

Like (0) Reply

Sorry for the inconvenience Boris. We are analyzing the problem. Will keep you posted once resolved.

Like (0) Reply

I have just been advised by the support over the email, that INSIGHTS APIs (both APM and RUM) are not yet supporting  OAUTH, and should be accessed via legacy authentication method.

 

Team is working on it currently, and will update us shortly.

 

Regards

Like (0) Reply

Apparently it has been fixed as of sSeptember 2019

Thank you team

Like (0) Reply

Was this post helpful?