Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

Restrict access to api's based on api keys

sudhap
New Member

Hello All,

I am a new learner to apigee and i am facing an issue with the aspect of the authorization using api keys.

So,basically I launched my developer portal with api's from swagger spec

signed in as a developer and

registered an app to a product, and my url(for dev portal) is like

http:://{orgname}-test. .. apigee.io

so my api's page look as :

7512-screenshot-from-2018-10-08-14-48-35.png

when sending a request from trace i.e from edge,when my url is :

htp://{orgname}-test. .. apigee.net

the verify api key policy functionality is visible but when hitting from developer portal the functionality is not working.

Like,though i included verify api key policy in apigee and also authorizations in swagger spec,the authorization is not being performed correctly.

So,i wanted to know:

1)How does the request from developer portal to hit an api reaches edge(based on url criteria)

2)What is the correct mechanism or flow to set the authorization via api key in apigee for restricting developers registered from developer portal.

Thanks

Solved Solved
0 5 455
1 ACCEPTED SOLUTION

In dev-portal/OAS your baseURL is still pointing to your original backend( Base URL: ci-cd-dpm-25190561.us-east-1.elb.amazonaws.com/ )

Update your swagger/oas in edge and add your Apigee proxy url as baseURL and update the portal.

7520-portal-aopigee.jpg

portal-aopigee.jpg

View solution in original post

5 REPLIES 5