Hi @songwen xie ,
When you say that your system needs "the developer and developer app information information that is stored at Apigee Edge cloud", what information are you referring to? Would that be the developer's name and email address? the name of the app?
This information is available to the API Proxy flow, after a VerifyApiKey policy, or after a VerifyAccessToken policy. At that point, the API proxy flow could inject a header into the request that is going to your backend, which contains this data.
When a developer uses the developer portal to register himself, and then create an app, this results in the creation of a developer entity in Apigee Edge, and then the creation of an app associated to that developer. The app is a key pair (client id and client secret) and a name, eg "App1" or whatever the developer has chosen.
At runtime, when the app sends an API request, if your API uses API key verification, then Apigee Edge automatically retrieves the name of the developer app for that client id, and can also retrieve the name and email of the developer . These data items are set into context variables that are available for any subsequent policy in the proxy flow. Something similar happens when the app uses an OAuth token.
To retrieve the developer name and email, you would need an AccessEntity policy, like this:
<AccessEntity name="GetDev">
<EntityType value="developer"/>
<EntityIdentifier ref="developer.id" type="developerid"/>
</AccessEntity>
The result is stored into a variable with a name derived from the policy name. In this case the variable is AccessEntity.GetDev. The resulting data is in XML format. To extract just the email you may wish to use an ExtractVariables policy, like so:
<ExtractVariables name="SetDeveloperProfile">
<Source>AccessEntity.GetDev</Source>
<VariablePrefix>dev</VariablePrefix>
<XMLPayload>
<Variable name="email" type="string">
<!-- parse an element from the developer profile using XPath. -->
<XPath>/Developer/Email</XPath>
</Variable>
</XMLPayload>
</ExtractVariables>You could then use AssignMessage to inject the necessary header into the request that will be sent to the backend:
<AssignMessage name='AssignMessage-1'>
<AssignTo createNew='false' type='request'/>
<Set>
<Headers>
<Header name='X-developerid'>{developer.id}</Header>
<Header name='X-developeremail'>{dev.email}</Header>
</Headers>
</Set>
</AssignMessage>
Your backend would then receive the headers X-developerid and X-developeremail.
This is covered in the doc for AccessEntity: http://apigee.com/docs/api-services/reference/access-entity-policy
LinkedIn
Twitter
