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 :
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! Go to 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.
portal-aopigee.jpg