"CustomMetaData" is empty in ${apiKeyRecord.xml} of "Lookup API Key"

[Suhas M V]

When I display the data saved in  ${apiKeyRecord.xml} by "Lookup API Key"  assertion, below XML is displayed. But in the XML i observed that CustomMetaData is empty. I was expecting the "custom fields" in this section. Can some one help me understand why is this section empty?

Note: I have created the application custom fields in portal and given the value.

 

<l7:ApiKey xmlns:l7="http://ns.l7tech.com/2012/04/api-management">
<l7:Key>l7xx390462367178282179379123123123</l7:Key>
<l7:Status>active</l7:Status>
<l7:AccountPlanMappingId>76</l7:AccountPlanMappingId>
<l7:LastUpdate>2018-02-28T04:00:02.147-05:00</l7:LastUpdate>
<l7:CustomMetaData>

 

</l7:CustomMetaData>
<l7:Apis>
<l7:Api apiId="d175225e-01a3-48ed-a0dd-123123124" planId="1db2438918912f57123123"/>
</l7:Apis>
<l7:Secret>e565c53ca0u1892123123</l7:Secret>
<l7:Label>TestApp</l7:Label>
<l7:Platform>Hybrid</l7:Platform>
<l7:Security>
<l7:OAuth>
<l7:CallbackUrl></l7:CallbackUrl>
<l7:Scope></l7:Scope>
<l7:Type></l7:Type>
</l7:OAuth>
</l7:Security>
</l7:ApiKey>

[Tomas Fencl]

I have done a bit of research on this and found that the API Plan XML that is by default sent to the APIGW from the portal is missing the information on custom properties completely. As the default plugin is using (a fairly undocumented) templating engine and the controller code is (fairly well) obfuscated I could not move any further from there.

 

I am considering building a custom API that would feed the portlaman with my custom XML to load also custom data to the APIKey record. Will post it here if I manage :-)