Azure API Management

Inside scoop from the API Management team

Release Notes – May 5th 2017

On Friday, May 5th, 2017, we started deploying a regular service update. We upgrade production service instances in batches, and it usually takes about a week for the rollout to complete.

Below is the list of improvements and bug fixes in this release.

New functionality

  • We have introduced a new policy allowing a customer to explicitly forward requests to their backend through an HTTP Proxy.

Updates and fixes

  • We now notify users through the developer portal when an API has a mock policy associated with it. Also with mocks, the status code you set in the policy is now checked to ensure it is a valid HTTP status code.
  • When exporting Swagger for an API, we will now include Security and SecurityDefinitions sections.
  • When exporting an Authenticated API endpoint from the developer portal, the user’s token information is now included in the service URL.
  • The minimum period for a Quota has been lowered from 60 minutes to 5 minutes.
  • Rate limits have been optimized for memory use.
  • We have made fixes in our support of Git – we now alpha-order “ref” sections in the files, and have made an update for Backend elements.
  • We made a fix relating to the correct calculation of effective policy when using a “base” element within a “choose” policy.
  • In the new Azure Portal, we made several updates, including allowing APIs to be added when defining Products, adding filtering to subscription lists, hiding secrets by default on the named values screen, and adding a redesigned VNET configuration screen.
  • The User Access Token resource is now available through our API – see example below.

To access the User Access Token resource:

POST /users/[youruserid]/token?api-version=2016-10-10 HTTP/1.1
Host: [yourservice].management.azure-api.net
Content-Type: application/json
If-Match: *
Authorization: SharedAccessSignature 
[youraccesstokengoeshere]
{
                "keyType": "primary",
                "expiry": "2017-05-09 18:20:08.7803554"
}

Response:
{
  "value": "[tokenishere]"
}