azure-api-management

问题 The certificate that came configured with our Azure API management endpoint expired today (apparently it was only valid for one year). How do we renew it? We thought that the point of using the default API management certificate provided by MS meant we did not have to manually worry about renewing it. But this appears not to be the case. expired certificate message 回答1: I believe this is a Microsoft/Azure issue, as Azure manages this certificate. I would recommend creating a ticket in the

问题 NOTE: SEE MY OWN ANSWER BELOW I have been looking through the slim documentation for hours. What I need is this: I have an incoming GET request from a system that can ONLY send GET requests. My back-end service requires a POST request. Can someone point me in the right direction in regards to what APIM policy I should be using or a combination of policies. I am using the policy reference but still can't come up with a decent solution: https://msdn.microsoft.com/en-us/library/azure/dn894081

问题 I am desperately trying to move 2 classic storage accounts from my old MSDN subscription to my MPN subscription and I keep hitting a brick wall as move is only supported for these through REST APIs. I have enabled the APIs following the instructions here.... https://azure.microsoft.com/en-us/documentation/articles/resource-group-move-resources/ and here... https://msdn.microsoft.com/en-us/library/azure/dn776326.aspx but am completely flummoxed. I have created a POST request as suggested to

问题 I underestand that when a request includes Ocp-Apim-Trace: true like below: GET /api/v1/BotConfig HTTP/1.1 Host: xyz.azure-api.net Cache-Control: no-cache Ocp-Apim-Trace: true Ocp-Apim-Subscription-Key: •••••••••••••••••••••••••••••••• The API Management adds ocp-apim-trace-location header: ocp-apim-trace-location: https://womewhere.blob.core.windows.net/apiinspectorcontainer/Hin6_SGFT-some-parameters This is obviously a security probelm and I am sure I am missing a point. What is the

问题 I underestand that when a request includes Ocp-Apim-Trace: true like below: GET /api/v1/BotConfig HTTP/1.1 Host: xyz.azure-api.net Cache-Control: no-cache Ocp-Apim-Trace: true Ocp-Apim-Subscription-Key: •••••••••••••••••••••••••••••••• The API Management adds ocp-apim-trace-location header: ocp-apim-trace-location: https://womewhere.blob.core.windows.net/apiinspectorcontainer/Hin6_SGFT-some-parameters This is obviously a security probelm and I am sure I am missing a point. What is the

问题 Can anyone suggest a REST API to fetch all the disks in a subscription according to the disk tier( eg- ultra,standard) and return a list of disks having the same tier. 回答1: As far as I know, there is no such API that could retrieve disks by disk tier(SKU) directly . You should filter the result yourself. If you are using .net , use Azure management SDK will be a way that much easier to get the result you need than using REST API. I write a simple console app for you, try the code below :

问题 I am leading a large team of azure functions developers. So, most of the examples quoted by Microsoft using the azure web interface don't work for me. I am developing Azure functions locally using emulators to save some costs. I publish all my functions through visual studio into my integration environment. I am developing a bunch of azure functions that need the api gateway to handle the authentication workflows using Azure AD B2C. Now, there's no api gateway emulator or an Azure AD B2C

问题 When I try to create an API in APIM by using Create from Function App , I fill out the fields and click Create . The operation provides the wait dots and comes back in five seconds and says Could not create an API. Please try again later. I can create a blank API...but not one from an existing Function App. I have tried multiple combinations, No products, all products, no version, version..etc. No luck. Thoughts? Notes The function in question is an HTTP Trigger. The function works locally on

问题 When I try to create an API in APIM by using Create from Function App , I fill out the fields and click Create . The operation provides the wait dots and comes back in five seconds and says Could not create an API. Please try again later. I can create a blank API...but not one from an existing Function App. I have tried multiple combinations, No products, all products, no version, version..etc. No luck. Thoughts? Notes The function in question is an HTTP Trigger. The function works locally on

问题 I have a question regarding the SCP claim after using Azure to register an API that I've developed. I've followed various tutorials and sample applications. Everything validates correctly and I'm able to call a API Method from a trusted subsystem using primarily this tutorial: https://github.com/AzureADSamples/WebApp-WebAPI-OAuth2-AppIdentity-DotNet The problem that I'm having is when I try to validate the SCP claim: Claim scopeClaim = ClaimsPrincipal.Current.FindFirst("http://schemas