Why do we see null values for developer, developer email of API requests in Postgres DB for VALIDATE org ?

[adevegowda]

We see the null values (not set) for developer, developer email for an API request made via developer portal on smart docs API Proxy of VALIDATE org in the Postgres DB (Analytics). Refer to the attached screenshot.

validate-org-analytics.png

However for the same request, these fields have proper values on our production environment.

Can someone please explain why ?

[adevegowda · Accepted solution]

After some investigation, I found the following information:

1. The VALIDATE org gets created automatically when you install smartdocs. You can find some more information here:
   
   • http://docs.apigee.com/private-cloud/latest/install-smartdocs
2. VALIDATE org is meant to host the "smartdocs" API Proxy. Whenever API requests are made via Developer Portal the API requests go through this smartdocs proxy, which subsequently routes these requests to the appropriate API Proxy meant for the specific org/env (For ex: org: myorg, env: production).
3. Essentially "smartdocs" API Proxy is just an interface between Developer Portal and the actual API Proxy deployed in an Edge org.
4. In the VALIDATE org, we will usually not have
   
   • any runtime APIs OR
   • developer, developer apps or API products configured
5. Hence, we will not have access_token, client_id, developer, developer email for smartdocs API Proxy. So these fields for "smartdocs" API Proxy will be shown as "not set".
6. As explained in point #1, the API requests are eventually routed to the actual API Proxy in another org. That is, the API requests are routed to myorg, so the fields such as access_token, client_id, developer and developer email will get populated with the proper values for actual API Proxy.