Usage of API-Key for validation

[rdas4]

Hi, i am looking for any document / guide which details the usage of API-Key. Following is the scenario:

 

An user will register itself using the API Gateway Portal. An API-Key will be generated for the user.

Same key will be send in the API request, which will be validated at the Gateway before accessing the back-end API.

 

Any specific assertion used to validate API-Key?

 

Regards.

 

[didsi01]

Is this what you are looking for Convert the Gateway Service - CA API Developer Portal - 3.5 - CA Technologies Documentation 

 

Look for the section " Line 10: Look Up API Key"  & "Lines 11-18: Check API key record found" in the documentation part.

[Alec Daniello]

Just to add on to the comment above....

 

If you publish an API from the Portal first, this policy logic will get laid down automatically. So it's the policy for the API itself that will enforce the logic behind API Key validation. The Look Up API Key assertion within the logic we're talking about, collects the API Key, and continues through to verify the key it found actually has access to the API. 

 

I hope this helps.

 

-Alec Daniello

APIM Support

[rdas4]

Thanks

[Shivashanthalatha Loganathan]

Hi All,

We are using Layer7 gateway version 10 and portal 4.5 version. We used Loopkup api key assertion and policy exactly as mentioned in the below URL , 
https://techdocs.broadcom.com/us/en/ca-enterprise-software/layer7-api-management/api-portal-legacy/3-5/set-up-the-api-portal/configure-service-policy-integration/convert-the-gateway-service.html

We are not able to get any context variables from that assertion .

<prefix>.found

<prefix>.key

<prefix>.plan

<prefix>.service

<prefix>.secret

<prefix>.status

<prefix>.xml
<prefix>.apiPlan

<prefix>.accountPlanMappingId

We verified the table  Generi_entity and found value_xml is empty for that association.
Could you pls help us to know whether this is Portal issue or any steps are missing to get the data.

Thanks,
Latha Loganathan