Skip Navigation
NOW AVAILABLE

Azure API Management updates—June 2020

Published date: 11 June, 2020

A regular Azure API Management service update was started on 10th June 2020 and included the following new features, bug fixes and changes, along with other improvements. It may take more than a week for your API Management service to receive the update.

New

  • Validate-jwt policy now supports RSA-signed and RSA-encrypted JWT validation, using uploaded certificate:
    • Issuer signing key’s certificate-id attribute specifies certificate entity identifier.
    • Issuer signing key’s n attribute specifies base64url-encoded RSA modulus.
    • Issuer signing key’s e attribute specifies base64url-encoded RSA exponent parameter.
    • Decryption key’s certificate-id attribute specifies certificate entity identifier.
  • API Management now supports decompression of zlib-wrapped deflate streams.
  • Self-hosted API gateway now supports logging JSON to the standard output.
  • Self-hosted API gateway now supports local telemetry logging to a DNS endpoint via UDP.

Changed

  • Metrics monitoring DNS zone is changed from .nsatc.net to .microsoftmetrics.com. The IP addresses of servers have not changed.
  • Node’s hostname is now included in the self-hosted API gateway’s heartbeat.
  • API Management now allows uploading certificates without a private key. The existence of a private key is checked during configuration changes (authenticate-certificate policy, backend entity and gateway’s hostnameConfiguration entity) and during runtime for policy expressions.
  • Application Insights telemetry properties have changed:
    • Apim Request Id custom property has been renamed to Request Id.
    • ApimanagementRegion custom property has been renamed to Region.
    • ApimanagementServiceName custom property has been renamed to Service Name.
    • Operation Name for the request telemetry is now in the format of api_id;rev=api_revision - operation_id if the API and operation are matched. Otherwise, the old format HTTP_VERB - request_url will be used.

The developer portal follows an independent release lifecycle and the per-release changelog is available on GitHub.

 

  • API Management
  • Features

Related Products