External Authorization - Analytics Feature - Apigee Edge

Question about External authorization: (according to the docs) if you use external authorization and a token generated by a 3rd party system you lose the benefit of analytics. However, you can still have Apigee validate the client id since that is created in Apigee. I plan to validate this, but is that correct? You still lose analytics if the token is not generated by Apigee, even though Apigee stores the token ?

~~Q:S:S~~

Solved Solved
0 1 283
1 ACCEPTED SOLUTION

Not applicable

Hi @Anil Sagar ,

Not true

#1 Once the access token is stored in Apigee, during runtime, it doesn't matter if that particular token is generated by apigee or an external system and it has no link with how data gets published to Analytics.

#2 You will not have any analytics data for the endpoints /authorize /token as Apigee doesn't expose those endpoints to generate tokens.

#3 You will have analytics data for the endpoints that you expose to your external system to store the externally generated auth codes, tokens etc in Apigee.

View solution in original post

1 REPLY 1

Not applicable

Hi @Anil Sagar ,

Not true

#1 Once the access token is stored in Apigee, during runtime, it doesn't matter if that particular token is generated by apigee or an external system and it has no link with how data gets published to Analytics.

#2 You will not have any analytics data for the endpoints /authorize /token as Apigee doesn't expose those endpoints to generate tokens.

#3 You will have analytics data for the endpoints that you expose to your external system to store the externally generated auth codes, tokens etc in Apigee.