How to get Product environment from request OauthV2 Credentails

[vysyarajusantos]

Hello folks,

How to know the API product details(name and environment) when I receive a request to generate Access Token? We know below details when we receive request but I would like to know the product details associated with the credentials. Could you please someone help me?

1. apigee.developer.app.name
2. apigee.developer.email
3. apigee.developer.id 

[dchiesa1 · Accepted solution]

You can gain access to such information within the API Proxy, using the AccessEntity policy. It will retrieve information based on the client_id. 

Example configuration

<AccessEntity name='AE-Developer-From-ClientID'>
  <EntityType value='developer' />
  <!-- 
    The thing referenced by the ref attribute must be the name of 
    a context variable containing a client ID (aka consumer key).
  -->
  <EntityIdentifier type='consumerkey' ref='client_id' />
</AccessEntity>

This documentation shows the data you get back from that policy.  It will get information about the developer, but not the app !

If you want information on the app, such as the app name, then you need a different AccessEntity policy. 

<AccessEntity name='AE-App-From-ClientID'>
  <EntityType value='app' />
  <EntityIdentifier type='consumerkey' ref='client_id' />
</AccessEntity>

This documentation shows what you get from that. It includes the app name. 

Why do you want this stuff?  Why is it important to know that stuff, before you issue the token? You get that information implicitly AFTER the token has been generated. So it seems ... unnecessary to explicitly query it, before you try to issue a token. 

[vysyarajusantos]

We deployed accesstoken as a separate API Proxy which generates accesstoken for multiple API proxies and we have 3 different environments for all of our applications. I would like to throw an error if i receive a request to qa loadbalancer url, qa accesstoken api proxy with dev credentials.

As accesstoken api proxy is common for multiple environments and multiple api proxies, I had to keep same accesstoken under "dev product" and "qa product". It generates access token even if we send cross environment credentials.

[dchiesa1]

I see.  OK that makes sense to me.