WSO2 API Manager 1.10.0 Released

The WSO2 API Manager 1.10.0 Released!

The WSO2 API Manager team is pleased to announce the release of version 1.10.0 of the Open Source API Manager.

WSO2 API Manager is a platform for creating, managing, consuming and monitoring APIs. It employs proven SOA best practices to solve a wide range of API management challenges such as API provisioning, API governance, API security and API monitoring. It combines some of the most powerful and mature components of the WSO2's state-of-the-art Carbon platform to deliver a smooth and end-to-end API management experience while catering to both API publisher and API consumer requirements.

WSO2 API Manager is comprised of several modules.

• API Provider: Define new APIs and manage them
• API Store: Browse published APIs and subscribe to them
• API Gateway: The underlying API runtime based on WSO2 ESB
• API Key Manager: Performs Key Generation and Key Validation functionalities

WSO2 API Manager is developed on top of the revolutionary WSO2 Carbon platform (Middleware a' la carte), an OSGi based framework that provides seamless modularity to your SOA via componentization. This release also contains many new features and a range of optional components (add-ons) that can be installed to customize the behavior of the API Manager. Further, any existing features of the product which are not required in your environment can be easily removed using the underlying provisioning framework of Carbon. In brief, WSO2 API Manager can be fully customized and tailored to meet your exact API management needs.

For more information on WSO2 API Manager please visit http://wso2.com/products/api-manager. Also take a look at the online product documentation.

How to Run

1. Extract the downloaded zip
2. Go to the bin directory in the extracted folder
3. Run the wso2server.sh or wso2server.bat as appropriate
4. Launch a web browser and navigate to https://localhost:9443/publisher to access the API provider webapp
5. Navigate to https://localhost:9443/store to access the API store
6. Navigate to https://localhost:9443/admin-dashboard to access Admin dashboard
7. Use "admin", "admin" as the username and password to login as an admin

New Features in 1.10.0

• [APIMANAGER-509] - Provide means to search tags
• [APIMANAGER-647] - Provide a better UI than selecting from a drop down list to deal with lifecycle states of an API with publisher UI
• [APIMANAGER-3705] - Add HTTP method "PATCH" support to API-M
• [APIMANAGER-3979] - Support Digest auth protected enpoint as a back end URL.
• [APIMANAGER-4027] - Enabling users to invoke APIs when the throttle limit has exceeded
• [APIMANAGER-4034] - Making the backend endpoint/url optional
• [APIMANAGER-4179] - Support reverse proxy for API manager admin-dashboard application
• [APIMANAGER-4192] - Set a throttling hard limit per API
• [APIMANAGER-4262] - REST API for publisher and there we are exposing a resource "/tiers"

Improvements in 1.10.0

• [APIMANAGER-2166] - DB2 Support
• [APIMANAGER-2514] - [APIM Migration] Improve instructions in README.txt for default embedded h2 db
• [APIMANAGER-2553] - Review the REST API
• [APIMANAGER-2661] - uri templates are allowed to be saved with invalid characters
• [APIMANAGER-2687] - Forum content and reply editting
• [APIMANAGER-3364] - Set correct registry permissions when the Publisher/Subscriber roles have been created by an external Identity Server
• [APIMANAGER-3591] - Throttle Policy management Enhacements
• [APIMANAGER-3638] - Make order of execution of APIManagerExtensionHandler and APIAuthenticationHandler configurable at each tenant
• [APIMANAGER-3951] - Store and return audit meta data for artifacts that are created or modified via published API calls
• [APIMANAGER-3958] - OAuth2 SCOPE value is not available in message path. It is better to set it as property?
• [APIMANAGER-3978] - /userinfo end point can be deployed as default API in the Gateway.
• [APIMANAGER-4112] - [Store REST API] New API to return APIs by tag
• [APIMANAGER-4114] - Renaming locations to which the store/publisher apps are being copied at build time
• [APIMANAGER-4124] - High number of DB calls going from Gateway to the database if default api is selected.
• [APIMANAGER-4144] - Fix the issue in API Migration client when we have blocked APIs
• [APIMANAGER-4146] - Integrate registry lifecycle with APIM 1.10.0
• [APIMANAGER-4189] - Introduce IDs for fields to enable EnjoyHint capabilities for the cloud tutorial
• [APIMANAGER-4217] - Sufficient Audit logs should be included for main activities in publisher, store
• [APIMANAGER-4383] - Change the error message into a meaningful one that get after exceeding the hard throttling limit in APIM logs.
• [APIMANAGER-4392] - Its better to make the wildcard charater mandatory for the publisher REST API query
• [APIMANAGER-4393] - APIM is not sending "Access-Control-Allow-Credentials" header in response.
• [APIMANAGER-4413] - Include different error codes when throttling out in different throttling levels
• [APIMANAGER-4414] - Add log messages to indicate when DAS reconnected with APIM and when DAS disconnected with APIM

Resolved Issues

• WSO2 API Manager V1.10.0 resolved issues

Key Features of WSO2 API Manager

Following is a categorization of the core features supported by WSO2 API Manager based on the target user group.

• Create a Store of all Available APIs:
  • Graphical experience similar to Android Marketplace or Apple App Store.
  • Browse APIs by provider, tags or name.
  • Self-registration to developer community to subscribe to APIs.
  • Subscribe to APIs and manage subscriptions on per-application basis.
  • Subscriptions can be at different service tiers based on expected usage levels.
  • Role based access to API Store; manage public and private APIs.
  • Manage subscriptions at a per-developer level.
  • Browse API documentation, download helpers for easy consumption.
  • Comment on and rate APIs.
  • Forum for discussing API usage issues (Available soon in future version).
  • Try APIs directly on the store front.
  • Internationalization (i18n) support.
• Publishing and Governing API Use:
  • Publish APIs to external consumers and partners, as well as internal users.
  • Supports publishing multiple protocols including SOAP, REST, JSON and XML style services as APIs.
  • Manage API versions and deployment status by version.
  • Govern...

WSO2 API Manager 1.10.0-rc4

v1.10.0-rc4

[maven-release-plugin] copy for tag v1.10.0-rc4

WSO2 API Manager 1.10.0-rc3

v1.10.0-rc3

[maven-release-plugin] copy for tag v1.10.0-rc3

WSO2 API Manager 1.10.0-rc2

v1.10.0-rc2

[maven-release-plugin] copy for tag v1.10.0-rc2

WSO2 API Manager 1.10.0-rc1

v1.10.0-rc1

[maven-release-plugin] copy for tag v1.10.0-rc1

WSO2 API Manager 1.10.0 - Beta Released !

WSO2 API Manager 1.10.0 - Beta Released !

Date : 14st December 2015

The WSO2 API Manager team is pleased to announce the release of WSO2 API Manager 1.10.0 Beta. You can download the distribution from [1].

WSO2 API Manager is a complete solution for designing and publishing APIs, creating and managing a developer community, and for scalably routing API traffic.

It leverages proven, production-ready integration, security, and governance components from the WSO2 Enterprise Service Bus, WSO2 Identity Server, and WSO2 Governance Registry.
In addition, it leverages the WSO2 Business Activity Monitor for Big Data analytics, giving you instant insight into APIs behavior.

We have fixed following JIRA issues

    Release Notes - WSO2 API Manager - Version 1.10.0-beta

Bug

• [APIMANAGER-1767] - Rating value cannot be seen by an anonymous user when gone to the API itself; But can be seen in the More APIs from "user" list
• [APIMANAGER-1809] - MYSQL Setup : ?relaxAutoCommit=true parameter needed
• [APIMANAGER-2376] - Tenant loading fails in Gateway after restarting the server, due to 'Resource does not exist at path /_system/config/repository/transports/https/listener'
• [APIMANAGER-2429] - [MT Mode] Google Analytics Configurations are applied only after server retstart
• [APIMANAGER-2717] - API status changes for subscriptions from other tenants are not updated (UI Issue)
• [APIMANAGER-3002] - Issue in the Documentation Content search in the Publisher and Store
• [APIMANAGER-3248] - SSO log out issue (publisher/store)
• [APIMANAGER-3370] - APIM retrieval of BAM data does not support DB2
• [APIMANAGER-3581] - WARN "LandingPageWebappDeployer Product landing page not found" when starting Beta pack
• [APIMANAGER-3706] - When you update an application in store and regenerate keys, still the application changes will not be replicated in IS side
• [APIMANAGER-3707] - Multiple versions of org.wso2.carbon.webapp.mgt.stub in wso2am-1.9.0-SNAPSHOT
• [APIMANAGER-3728] - Swagger Import button in publisher should be validated
• [APIMANAGER-3786] - Fix for 'claim mapping attribute getting null' issue is not updated in api manager side
• [APIMANAGER-3789] - Cannot access url type of myapi/v1.0/param/ of the API created with URL template like {pparam}/*
• [APIMANAGER-3830] - When you configure IS as KM, during the start up few errors will be printed.
• [APIMANAGER-3902] - custom configured throttling tier doesn't apply for application level for tenants
• [APIMANAGER-3913] - when JWT caching is enabled prototype APIs cannot be invoked
• [APIMANAGER-3920] - [Intermittent] - "org.wso2.carbon.registry.core.exceptions.ResourceNotFoundException: Resource does not exist at path /_system/config" returned when loading tenant store with APIs
• [APIMANAGER-3925] - Error occurs when approving/rejecting subscriptions creation (workflow) using admin dash board
• [APIMANAGER-3962] - HEAD method returns 500
• [APIMANAGER-3968] - jdbc table not created when db2 is used for statistics tables
• [APIMANAGER-3992] - API Store top menu bar went missing when navigating through the pages of "Applications" page
• [APIMANAGER-3996] - Even when Production Key and Production gateway options are selected from API Console, the request always goes to Sandbox gateway
• [APIMANAGER-4008] - AppId is not available in ApplicationWorkflowDTO
• [APIMANAGER-4011] - TenantId defaults to 0 instead of -1 (MultitenantConstants.INVALID_TENANT_ID) in AbstractAPIManager
• [APIMANAGER-4020] - JWT should be encoded with base64url
• [APIMANAGER-4058] - Publisher implementation page, "Test" URL buttons give "invalid" for valid URLs
• [APIMANAGER-4061] - API Publisher context not validated properly
• [APIMANAGER-4071] - After removing subscription, a Production/Sandbox blocked API for the particular App cannot be unblocked again
• [APIMANAGER-4076] - UI Issues with Publisher API Docs page
• [APIMANAGER-4077] - If two docs were added to an API with the same file name, first file will be overwritten by the second.
• [APIMANAGER-4080] - Visibility parameter is ignored when adding api through the API(addAPI)
• [APIMANAGER-4086] - Destination Based Stat publishing cannot be disabled by admin-dashboard
• [APIMANAGER-4087] - Previously populated values disappear when re-enabling Stats
• [APIMANAGER-4089] - Error with subscription
• [APIMANAGER-4091] - Handling Location header is different in API Manager compared to ESB
• [APIMANAGER-4095] - The enduser claim sent it JWT for NTML grant type is wrong
• [APIMANAGER-4108] - Server startup exception - A queue manager instance has already been set
• [APIMANAGER-4116] - In registry wsdl enpoint url has api version appended twice
• [APIMANAGER-4121] - Prototyped APIs cannot be searched on API Store
• [APIMANAGER-4123] - Error when accessing Statistics when statistics DB is PostgreSQL
• [APIMANAGER-4127] - API Publisher Statistics "faulty invocations" and "API response times"
• [APIMANAGER-4134] - Need to check the gateway type before adding custom sequences into registry
• [APIMANAGER-4137] - If tenant name is too long then tenant API store will show tenant names in abnormal way
• [APIMANAGER-4139] - My Subscription page Fails to load when an API is Recreated After Deleting
• [APIMANAGER-4140] - API Manager migration client stops migration of artifacts if there are blocked state APIS
• [APIMANAGER-4141] - Gateway url of swagger console is not changing after entering custom url.
• [APIMANAGER-4145] - Queries in APIUsageStatisticsClient should be compatible with Oracle/H2/MSSQL/PostgreSQL databases, in addition to MySQL.
• [APIMANAGER-4148] - Errors when loading APIM statistic pages with oracle
• [APIMANAGER-4149] - API Forum appears only if there is at least one active tenant
• [APIMANAGER-4154] - URI template, query parameters are url-encoded by default
• [APIMANAGER-4155] - API Throttled out graphs shows invalid data when there are cross tenant invocations
• [

WSO2 API Manager 1.10.0 Alpha

    Release Notes - WSO2 API Manager - Version 1.10.0-alpha

Bug Fixed

• [APIMANAGER-1767] - Rating value cannot be seen by an anonymous user when gone to the API itself; But can be seen in the More APIs from "user" list
• [APIMANAGER-1809] - MYSQL Setup : ?relaxAutoCommit=true parameter needed
• [APIMANAGER-2376] - Tenant loading fails in Gateway after restarting the server, due to 'Resource does not exist at path /_system/config/repository/transports/https/listener'
• [APIMANAGER-2429] - [MT Mode] Google Analytics Configurations are applied only after server retstart
• [APIMANAGER-3581] - WARN "LandingPageWebappDeployer Product landing page not found" when starting Beta pack
• [APIMANAGER-3706] - When you update an application in store and regenerate keys, still the application changes will not be replicated in IS side
• [APIMANAGER-3707] - Multiple versions of org.wso2.carbon.webapp.mgt.stub in wso2am-1.9.0-SNAPSHOT
• [APIMANAGER-3728] - Swagger Import button in publisher should be validated
• [APIMANAGER-3830] - When you configure IS as KM, during the start up few errors will be printed.
• [APIMANAGER-3902] - custom configured throttling tier doesn't apply for application level for tenants
• [APIMANAGER-3913] - when JWT caching is enabled prototype APIs cannot be invoked
• [APIMANAGER-3992] - API Store top menu bar went missing when navigating through the pages of "Applications" page
• [APIMANAGER-3996] - Even when Production Key and Production gateway options are selected from API Console, the request always goes to Sandbox gateway
• [APIMANAGER-4008] - AppId is not available in ApplicationWorkflowDTO
• [APIMANAGER-4011] - TenantId defaults to 0 instead of -1 (MultitenantConstants.INVALID_TENANT_ID) in AbstractAPIManager
• [APIMANAGER-4058] - Publisher implementation page, "Test" URL buttons give "invalid" for valid URLs
• [APIMANAGER-4076] - UI Issues with Publisher API Docs page
• [APIMANAGER-4077] - If two docs were added to an API with the same file name, first file will be overwritten by the second.
• [APIMANAGER-4080] - Visibility parameter is ignored when adding api through the API(addAPI)
• [APIMANAGER-4087] - Previously populated values disappear when re-enabling Stats
• [APIMANAGER-4108] - Server startup exception - A queue manager instance has already been set
• [APIMANAGER-4116] - In registry wsdl enpoint url has api version appended twice
• [APIMANAGER-4121] - Prototyped APIs cannot be searched on API Store
• [APIMANAGER-4123] - Error when accessing Statistics when statistics DB is PostgreSQL
• [APIMANAGER-4134] - Need to check the gateway type before adding custom sequences into registry
• [APIMANAGER-4137] - If tenant name is too long then tenant API store will show tenant names in abnormal way
• [APIMANAGER-4139] - My Subscription page Fails to load when an API is Recreated After Deleting
• [APIMANAGER-4145] - Queries in APIUsageStatisticsClient should be compatible with Oracle/H2/MSSQL/PostgreSQL databases, in addition to MySQL.
• [APIMANAGER-4148] - Errors when loading APIM statistic pages with oracle
• [APIMANAGER-4154] - URI template, query parameters are url-encoded by default
• [APIMANAGER-4155] - API Throttled out graphs shows invalid data when there are cross tenant invocations
• [APIMANAGER-4156] - When Stats DB type is Oracle few graphs are delayed about 10 seconds when loading
• [APIMANAGER-4163] - API Manager store creates sessions for non-existing resources
• [APIMANAGER-4167] - Error when store debug logs are enabled
• [APIMANAGER-4170] - Error in key generation when PostgreSQL used as the database
• [APIMANAGER-4172] - API Console breaks, if double quotes are used for names/labels in the swagger definition
• [APIMANAGER-4176] - Sample Weather API no longer works
• [APIMANAGER-4178] - Error when try to enable 'code' grant type from Manage->Oauth menu in management console
• [APIMANAGER-4190] - bussiness owner information chinese incorrect code.
• [APIMANAGER-4197] - JWT token invalid enduser value
• [APIMANAGER-4205] - Cannot create (publish) API
• [APIMANAGER-4208] - API Creation fail in tenant mode

Improvement

• [APIMANAGER-2687] - Forum content and reply editting
• [APIMANAGER-3591] - Throttle Policy management Enhacements
• [APIMANAGER-3638] - Make order of execution of APIManagerExtensionHandler and APIAuthenticationHandler configurable at each tenant
• [APIMANAGER-4112] - [Store REST API] New API to return APIs by tag
• [APIMANAGER-4114] - Renaming locations to which the store/publisher apps are being copied at build time
• [APIMANAGER-4124] - High number of DB calls going from Gateway to the database if default api is selected.
• [APIMANAGER-4189] - Introduce IDs for fields to enable EnjoyHint capabilities for the cloud tutorial

New Feature

• [APIMANAGER-509] - Provide means to search tags
• [APIMANAGER-647] - Provide a better UI than selecting from a drop down list to deal with lifecycle states of an API with publisher UI
• [APIMANAGER-3979] - Support Digest auth protected enpoint as a back end URL.
• [APIMANAGER-4027] - Enabling users to invoke APIs when the throttle limit has exceeded
• [APIMANAGER-4179] - Support reverse proxy for API manager admin-dashboard application

WSO2 API Manager 1.9.1 Released

WSO2 API Manager team is pleased to announce the release of WSO2 API Manager 1.9.1. 

WSO2 API Manager is a platform for creating, managing, consuming and monitoring APIs. It employs proven SOA best practices to solve a wide range of API management challenges such as API provisioning, API governance, API security and API monitoring. It combines some of the most powerful and mature components of the WSO2's state-of-the-art Carbon platform to deliver a smooth and end-to-end API management experience while catering to both API publisher and API consumer requirements.

WSO2 API Manager is comprised of several modules.

• API Provider: Define new APIs and manage them
  
• API Store: Browse published APIs and subscribe to them
  
• API Gateway: The underlying API runtime based on WSO2 ESB
  
• API Key Manager: Performs Key Generation and Key Validation functionalities
  

WSO2 API Manager is developed on top of the revolutionary WSO2 Carbon platform, an OSGi based framework that provides seamless modularity to your SOA via componentization. This release also contains many new features and a range of optional components (add-ons) that can be installed to customize the behavior of the API Manager. Further, any existing features of the product which are not required in your environment can be easily removed using the underlying provisioning framework of Carbon. In brief, WSO2 API Manager can be fully customized and tailored to meet your exact API management needs.

For more information on WSO2 API Manager and to download the product please visit http://wso2.com/products/api-manager. Also take a look at the online product documentation.

How to Run

1. Extract the downloaded zip
   
2. Go to the bin directory in the extracted folder
   
3. Run the wso2server.sh or wso2server.bat as appropriate
   
4. Launch a web browser and navigate to https://localhost:9443/publisher to access the API provider webapp
   
5. Navigate to https://localhost:9443/store to access the API store
   
6. Navigate to https://localhost:9443/admin-dashboard to access Admin dashboard
   
7. Use "admin", "admin" as the username and password to login as an admin
   

This release doesn't contain new features or major architectural changes from the last release & only includes bug fixes and improvements. Users should be able to move onto the newer version from 1.9.0 without any data Migration. 

Following Bug Fixes and Improvements are included in this release.

Improvements 

• Improvements

Bug Fixes 

• Bug Fixes

Key Features of WSO2 API Manager

Following is a categorization of the core features supported by WSO2 API Manager based on the target user group.

Design and Prototype APIs:

• Design APIs, gather developer's feedback before implementing (API First Design).
  
• Design can be done from the publishing interface or via importing an existing swagger definition
  
• Deploy a prototyped API, provide early access to APIs, and get early feedback.
  
• Mock API implementation using Javascript.
  
• Support publishing SOAP, REST, JSON and XML style services as XML.
  

Create a Store of all Available APIs:

• Graphical experience similar to Android Marketplace or Apple App Store.
  
• Browse APIs by provider, tags or name.
  
• Self-registration to developer community to subscribe to APIs.
  
• Subscribe to APIs and manage subscriptions on per-application ba...

WSO2 API Manager 1.9.1 Beta Released

The WSO2 API Manager team is pleased to announce the Beta release of version 1.9.1 of the Open Source API Manager.

This release doesn't contain new features or major architectural changes from the last release & only includes bug fixes and minor improvements. Users should be able to move onto the newer version from 1.9.0 without any data Migration.

Following Bug Fixes and Improvements are included in this release.

Bugs

• Bug Fixes

Improvements

• Improvements

Documentation can be found at [1]. We encourage you to report issues, suggestions and improvements related to API Manager through public Jira [2]. When reporting issues, please report under version 1.9.1 Beta

[1] https://docs.wso2.com/display/AM191/WSO2+API+Manager+Documentation
[2] https://wso2.org/jira/browse/APIMANAGER

WSO2 API Manager 1.9.0 Released

The WSO2 API Manager team is pleased to announce the release of version 1.9.0 of the Open Source API Manager.

For more information on WSO2 API Manager and to download the product please visit http://wso2.com/products/api-manager. Also take a look at the online product documentation.

API Manager 1.9.0 includes following new features, improvements and bug fixes.

New Features

• [APIMANAGER-3286] - Enable using an external Authorization Server for Key Validation/ Creation
• [APIMANAGER-3498] - Create a corresponding SP when creating OAuth Application from Store UI
• [APIMANAGER-3398] - Sharing capabilities for Applications (subscriptions)
• [APIMANAGER-3397] - Pluggable Versioning Strategy
• [APIMANAGER-3388] - Update API Manager to the latest Swagger version (2.0)
• [APIMANAGER-3334] - Custom URLs support for APIPublisher/APIStore
• [APIMANAGER-3339] - Add missing event attributes in publishing data to BAM/CEP
• [APIMANAGER-3344] - Scope specific access token generation from API Store
• [APIMANAGER-3415] - Providing a way to add event receiver and analyser configurations through UI in APIM
• [APIMANAGER-3456] - User password change feature for API Store
• [APIMANAGER-3487] - API Migration Client to migrate APIM 1.8.0 to 1.9.0
• [APIMANAGER-2238] - [UI improvement] Ability to specify the token scope in Store when generating Application Token

Improvements

• [APIMANAGER-772] - Add integration tests for the new feature Make JWT generation configurable
• [APIMANAGER-1335] - Create Script to Test Visibility in Public, Private Restricted APIs
• [APIMANAGER-1603] - Same configuration and description for Thrift Key Validation server host name is mentioned twice in api-manager.xml
• [APIMANAGER-1704] - Do we need to expose OPTIONS request in the UI?
• [APIMANAGER-1740] - Documentatoin links added should be visible as links in store.
• [APIMANAGER-1765] - [Store-APIs] Tier availability for an API is not returned in the set of apis returned when called the store/site/blocks/api/listing/ajax/list.jag
• [APIMANAGER-1948] - These junit test cases testUpdateRefreshedApplicationAccessToken and testIsAccessTokenExists need to added back to apimgt.impl module
• [APIMANAGER-2010] - For non-subscribed APIs, need to have “Default” application pre-selected in subscribe UI
• [APIMANAGER-2270] - Upgrade wso2's jQuery version to 1.9.0 or greater
• [APIMANAGER-2543] - velosity log file should move to repository logs directory
• [APIMANAGER-2787] - Mis-spellings in the code for 'tenant' as 'tennat'
• [APIMANAGER-2854] - Remove message logging from APIManagerExtensionHandler
• [APIMANAGER-2880] - API Store: Need indication on the API page that I am already subscribed to the API
• [APIMANAGER-2910] - helpful troubleshooting message?
• [APIMANAGER-2954] - Publishing an api to an external store
• [APIMANAGER-3069] - There is no option displayed to delete added Swagger API definition parameters
• [APIMANAGER-3092] - Issue in the API doc visibility - 'Private'
• [APIMANAGER-3143] - Need to remove author info from API Cloud
• [APIMANAGER-3198] - Change gateway response messages on failures to more descriptive descriptions
• [APIMANAGER-3199] - Change log level on gateway call rejection from ERROR to INFO when there is no actual failure
• [APIMANAGER-3203] - Moving API Usage Publisher stream names and versions to read from config file.
• [APIMANAGER-3231] - Debugs logs not wrapped by isDebugEnabled check
• [APIMANAGER-3235] - OPTIONS method is shown in the API Console
• [APIMANAGER-3255] - Introduce a Publisher API to import swagger definition using a file or a URL
• [APIMANAGER-3292] - Publisher "Edit Swagger Definition" : Add grammar check
• [APIMANAGER-3293] - Publisher "Edit Swagger Definition" : Resizable popup
• [APIMANAGER-3311] - There is no API to retrieve an API Document by File
• [APIMANAGER-3319] - There is no API to retrieve the endpoints of an API Store Item
• [APIMANAGER-3324] - Presentation of Sandbox/Production URL not clear
• [APIMANAGER-3328] - Remove 'Visible to my domain' visibility when in single tenant mode
• [APIMANAGER-3329] - Modify hostname/port to be taken from variables in Token API and Revoke API xmls
• [APIMANAGER-3330] - Modify hostname/port to be taken from variables in Token API,Revoke API and Authorize xmls
• [APIMANAGER-3333] - Fixing hardcoded username and password issue in api-manager.xml and make them resolved by user-mgt.xml
• [APIMANAGER-3336] - Improve the SAML2BearerGrantHandler with role based scope validation by extracting roles from SAML2 Assertion
• [APIMANAGER-3351] - Improving Statistics graphs
• [APIMANAGER-3366] - Improve publishing to multiple Gateways feature
• [APIMANAGER-3392] - New API - Get list of tags for a API
• [APIMANAGER-3393] - New API - Get list of tiers available for API
• [APIMANAGER-3394] - New API - List of all available tiers in API-M deployment
• [APIMANAGER-3395] - Need to provide proper instructions when adding tags to apis
• [APIMANAGER-3396] - HTTP Head method Support with APIM
• [APIMANAGER-3399] - Pre-populate API Manager with one API which can be used OOTB
• [APIMANAGER-3400] - Add pagination to 'My Subscriptions' page
• [APIMANAGER-3401] - UI imrpovements to APIPublisher Stats page
• [APIMANAGER-3402] - Improve the message prompted when deleting applications to state whether that app has active subscriptions or not
• [APIMANAGER-3420] - Swagger v2.0 support for APIM