I added below string in the call back URI field in the application creation in edge
" Callback URL : https://localhost,https://yahoo.com " .
And when Tried to use https://localhost or https://localhost as redirect_uri while generating authcode or access token it works fine.
Just want to make sure it is intended functionality that I can leverage.
Hi @krishna.prasadm . Good question. We’ve run into this type of requirement in the past and as Anil commented, multiple URLs are not supported. However, there’s a workaround. You can leave the callback URL blank and leverage JavaScript Policies to validate the URLs. Please take a look at this document Designating multiple callback URLs. http://apigee.com/docs/api-services/content/advanced-oauth-20-topics.
Please let us know your experience with this feature :-). Hope it helps.
Thanks for the answer, for some reason authcode policy checking the substring from call back URI field that is the reason i am able to put comma separated URLs and make it work .But as you said the filed should contain conceptually.
I added below string in the call back URI field in the application creation in edge
" Callback URL : https://localhost,https://yahoo.com " .
And when Tried to use https://localhost or https://localhost as redirect_uri while generating authcode or access token it works fine.
Just want to make sure it is intended functionality that I can leverage.