[Announce] WSO2 API Manager 1.8.0 Released !

Vijayaratha Vijayasingam rathav at wso2.com
Tue Dec 16 06:12:34 PST 2014

The WSO2 API Manager 1.8.0 Released!

The WSO2 API Manager team is pleased to announce the release of version
1.8.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

WSO2 API Manager is developed on top of the revolutionary WSO2 Carbon
platform <http://wso2.org/projects/carbon> (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
   7. Use "admin", "admin" as the username and password to login as an admin

Improvements in 1.8.0

   - [APIMANAGER-637 <https://wso2.org/jira/browse/APIMANAGER-637>] -
   Provide means to search APIs 'starting with' / 'ending with' certain
   - [APIMANAGER-702 <https://wso2.org/jira/browse/APIMANAGER-702>] - Time
   of subscription is not saved
   - [APIMANAGER-1347 <https://wso2.org/jira/browse/APIMANAGER-1347>] -
   Published APIs shouldn't show details of proxied web services
   - [APIMANAGER-1368 <https://wso2.org/jira/browse/APIMANAGER-1368>] - API
   Manager Publisher WSDL for API should change end point to gateway
   - [APIMANAGER-2142 <https://wso2.org/jira/browse/APIMANAGER-2142>] -
   Better to have option to save the wsdl in registry or keep it as url
   - [APIMANAGER-2158 <https://wso2.org/jira/browse/APIMANAGER-2158>] -
   Logging error when Single Logout is disabled
   - [APIMANAGER-2552 <https://wso2.org/jira/browse/APIMANAGER-2552>] -
   Inactive tenants can still access resources exposed through NIO transport
   - [APIMANAGER-2557 <https://wso2.org/jira/browse/APIMANAGER-2557>] -
   Configure Audit Log in log4j.properties
   - [APIMANAGER-2565 <https://wso2.org/jira/browse/APIMANAGER-2565>] -
   Application is allowed to Delete when it is already in the Workflow
   Approval Process.
   - [APIMANAGER-2570 <https://wso2.org/jira/browse/APIMANAGER-2570>] -
   Publisher's update API page's error Messages should be informative
   - [APIMANAGER-2593 <https://wso2.org/jira/browse/APIMANAGER-2593>] -
   According to the making API changes, Existing WSDL docs on registry should
   be updated
   - [APIMANAGER-2635 <https://wso2.org/jira/browse/APIMANAGER-2635>] -
   Case insensitive username comparison for APIM
   - [APIMANAGER-2650 <https://wso2.org/jira/browse/APIMANAGER-2650>] - The
   publisher URL/API Console does not work out of the box if you set a port
   - [APIMANAGER-2652 <https://wso2.org/jira/browse/APIMANAGER-2652>] -
   RestPeopleTestCase fails
   - [APIMANAGER-2694 <https://wso2.org/jira/browse/APIMANAGER-2694>] -
   Make recently added API loading asynchronous
   - [APIMANAGER-2711 <https://wso2.org/jira/browse/APIMANAGER-2711>] -
   Make JWTGenerator Extensible
   - [APIMANAGER-2755 <https://wso2.org/jira/browse/APIMANAGER-2755>] -
   Migration tool to modify apis to migrate from 1.6 to 1.7
   - [APIMANAGER-2785 <https://wso2.org/jira/browse/APIMANAGER-2785>] -
   Provide support for self signup for tenants' APIStores
   - [APIMANAGER-2788 <https://wso2.org/jira/browse/APIMANAGER-2788>] -
   HTTP, HTTPS url redirection for login call in publisher
   - [APIMANAGER-2790 <https://wso2.org/jira/browse/APIMANAGER-2790>] -
   Improvements for private API fix
   - [APIMANAGER-2795 <https://wso2.org/jira/browse/APIMANAGER-2795>] - AM
   still using GenericArtifactManager for search function.
   - [APIMANAGER-2796 <https://wso2.org/jira/browse/APIMANAGER-2796>] - API
   Category description and thumbnail images are hard coded.
   - [APIMANAGER-2836 <https://wso2.org/jira/browse/APIMANAGER-2836>] -
   Applying cassandra data purging related modifications to API-M toolbox
   - [APIMANAGER-2851 <https://wso2.org/jira/browse/APIMANAGER-2851>] - Log
   Http Status code in APIManagerExtensionHandler
   - [APIMANAGER-2906 <https://wso2.org/jira/browse/APIMANAGER-2906>] -
   tiers - show the tier quota as a tooltip description
   - [APIMANAGER-2939 <https://wso2.org/jira/browse/APIMANAGER-2939>] - Add
   a help text to describe API document based visibility levels
   - [APIMANAGER-2953 <https://wso2.org/jira/browse/APIMANAGER-2953>] -
   Allow variable names for http endpoints from Publisher UI
   - [APIMANAGER-2963 <https://wso2.org/jira/browse/APIMANAGER-2963>] -
   Make the endpoint 'Test' button work for endpoints which doesn't support
   - [APIMANAGER-2964 <https://wso2.org/jira/browse/APIMANAGER-2964>] -
   Performance improvment on API Store MySubscriptions page
   - [APIMANAGER-3017 <https://wso2.org/jira/browse/APIMANAGER-3017>] -
   Display notification to remove APIs from external stores when API is not in
   PUBLISHED state

Bug Fixes

   - [APIMANAGER-753 <https://wso2.org/jira/browse/APIMANAGER-753>] -
   Testcases failed in gateway bundle in APIKeyCacheTest ,
   OAuthAuthenticatorTest and APIManagerExtensionHandlerTest
   - [APIMANAGER-891 <https://wso2.org/jira/browse/APIMANAGER-891>] -
   APISecurityException when load testing: Invalid use of
   SingleClientConnManager: connection still allocated.
   - [APIMANAGER-983 <https://wso2.org/jira/browse/APIMANAGER-983>] -
   synapse generating wrong URL when calling API
   - [APIMANAGER-1260 <https://wso2.org/jira/browse/APIMANAGER-1260>] -
   Email ID login does not support in multi tenancy mode
   - [APIMANAGER-1747 <https://wso2.org/jira/browse/APIMANAGER-1747>] -
   Indicate as "invalid" when validate https endpoint URI's
   - [APIMANAGER-1816 <https://wso2.org/jira/browse/APIMANAGER-1816>] -
   publisher login does not redirect to home
   - [APIMANAGER-1830 <https://wso2.org/jira/browse/APIMANAGER-1830>] -
   Gateway key-cache does not get invalidated with revoke token api call and
   refresh_token api call-only for tenant mode
   - [APIMANAGER-1862 <https://wso2.org/jira/browse/APIMANAGER-1862>] -
   User Token is still generated even when an additional character is appended
   at the end of the base 64 encoded value
   - [APIMANAGER-1864 <https://wso2.org/jira/browse/APIMANAGER-1864>] -
   Access token generation fails when username and password are similar
   - [APIMANAGER-1886 <https://wso2.org/jira/browse/APIMANAGER-1886>] - API
   Can be invoked after removing subscription
   - [APIMANAGER-1887 <https://wso2.org/jira/browse/APIMANAGER-1887>] - Can
   invoke API even after removing the subscription application
   - [APIMANAGER-1895 <https://wso2.org/jira/browse/APIMANAGER-1895>] -
   javax.net.ssl.SSLException when sending request in http
   - [APIMANAGER-1910 <https://wso2.org/jira/browse/APIMANAGER-1910>] -
   [Failover endpoint] When production endpoint is down, api invocation fails
   - [APIMANAGER-1926 <https://wso2.org/jira/browse/APIMANAGER-1926>] -
   WADL url is showing under "show more option" when select the wsdl Endpoint
   - [APIMANAGER-1998 <https://wso2.org/jira/browse/APIMANAGER-1998>] -
   Search in api store/ doesn't work when user is not logged in
   - [APIMANAGER-2000 <https://wso2.org/jira/browse/APIMANAGER-2000>] -
   Using wso2 default Dialect for the User Sign up
   - [APIMANAGER-2032 <https://wso2.org/jira/browse/APIMANAGER-2032>] - API
   Manager 1.6.0 error on BAM with not autenticated users
   - [APIMANAGER-2048 <https://wso2.org/jira/browse/APIMANAGER-2048>] -
   Cannot view any sequence in the Main -> Manage -> Sequences page in the
   Carbon Management Console
   - [APIMANAGER-2058 <https://wso2.org/jira/browse/APIMANAGER-2058>] -
   [UI] Production Endpoint label says "endpointUi.Production Endpoint"
   - [APIMANAGER-2086 <https://wso2.org/jira/browse/APIMANAGER-2086>] -
   APIs published to external stores shows incorrect original publisher in
   Recently added API list
   - [APIMANAGER-2103 <https://wso2.org/jira/browse/APIMANAGER-2103>] -
   When you click on Edit tab of the api details page in API publisher it does
   not go to the edit wizard
   - [APIMANAGER-2116 <https://wso2.org/jira/browse/APIMANAGER-2116>] -
   Error when logging out of SSO enabled Management console
   - [APIMANAGER-2173 <https://wso2.org/jira/browse/APIMANAGER-2173>] -
   Error in pom.xml
   - [APIMANAGER-2194 <https://wso2.org/jira/browse/APIMANAGER-2194>] -
   Unable to edit a created API
   - [APIMANAGER-2231 <https://wso2.org/jira/browse/APIMANAGER-2231>] -
   [intermittent] [BAM] Published data does not get written in to database due
   to constraint violation exception
   - [APIMANAGER-2250 <https://wso2.org/jira/browse/APIMANAGER-2250>] -
   Error occurs when starting up carbon after a new role is added
   - [APIMANAGER-2260 <https://wso2.org/jira/browse/APIMANAGER-2260>] -
   Remove JS alerts added to the Publisher/Store UIs
   - [APIMANAGER-2282 <https://wso2.org/jira/browse/APIMANAGER-2282>] -
   Publisher does not work in IE9
   - [APIMANAGER-2323 <https://wso2.org/jira/browse/APIMANAGER-2323>] -
   Swagger console does not work in IE (10)
   - [APIMANAGER-2331 <https://wso2.org/jira/browse/APIMANAGER-2331>] -
   When login using SSO to APIM, if we have given wrong password for login, it
   doesn't give error message, neither from back end side.
   - [APIMANAGER-2350 <https://wso2.org/jira/browse/APIMANAGER-2350>] -
   java.lang.IndexOutOfBoundsException returned when searching for a
   non-existing API through the store UI
   - [APIMANAGER-2414 <https://wso2.org/jira/browse/APIMANAGER-2414>] - NPE
   thrown when resubmitting the API to external store
   - [APIMANAGER-2418 <https://wso2.org/jira/browse/APIMANAGER-2418>] -
   Please update the token percister class name to
   in api-manager.xml
   - [APIMANAGER-2453 <https://wso2.org/jira/browse/APIMANAGER-2453>] -
   Published APIs do not appear on store under "APIs". Only listed "Recently
   Added" section in a clustered setup with all nodes fronted by an ELB
   - [APIMANAGER-2454 <https://wso2.org/jira/browse/APIMANAGER-2454>] -
   <WebContextRoot> not applicable for publisher/store apps
   - [APIMANAGER-2464 <https://wso2.org/jira/browse/APIMANAGER-2464>] - No
   matching resource found in the API for the given request thrown when
   invoking the Prototype API
   - [APIMANAGER-2468 <https://wso2.org/jira/browse/APIMANAGER-2468>] -
   WSO2 API Manager: “Try it out” does not work when only HTTPS is selected
   - [APIMANAGER-2474 <https://wso2.org/jira/browse/APIMANAGER-2474>] -
   WARN - APIConsumerImpl Failed to retrieve recently added API query when
   accessing tenant's API store
   - [APIMANAGER-2481 <https://wso2.org/jira/browse/APIMANAGER-2481>] -
   Response content-type cannot be changed - revert back to application/json
   - [APIMANAGER-2482 <https://wso2.org/jira/browse/APIMANAGER-2482>] - URL
   redirection issue
   - [APIMANAGER-2486 <https://wso2.org/jira/browse/APIMANAGER-2486>] -
   Error occurred while running CacheCleanupTask
   - [APIMANAGER-2487 <https://wso2.org/jira/browse/APIMANAGER-2487>] -
   Sequence edit link directs to dead page and exceptions thrown.
   - [APIMANAGER-2499 <https://wso2.org/jira/browse/APIMANAGER-2499>] -
   Topic content and reply content are not validated for empty content.
   - [APIMANAGER-2502 <https://wso2.org/jira/browse/APIMANAGER-2502>] -
   Replies to forum topics with empty strings get saved.
   - [APIMANAGER-2503 <https://wso2.org/jira/browse/APIMANAGER-2503>] -
   Access token exchange for SAML2 Assertion fails for APIM 1.7.0 + IS 5.0.0
   - [APIMANAGER-2504 <https://wso2.org/jira/browse/APIMANAGER-2504>] -
   HTTP and HTTPS transport when creating API in publisher
   - [APIMANAGER-2506 <https://wso2.org/jira/browse/APIMANAGER-2506>] -
   When changing the type from 'Other' to any of the remaining types,
   mandatory text filed does not get hide so that the API docs cannot be
   - [APIMANAGER-2507 <https://wso2.org/jira/browse/APIMANAGER-2507>] -
   Cannot create API docs if changing the type to “File” then to
   “In-Line” Source
   - [APIMANAGER-2509 <https://wso2.org/jira/browse/APIMANAGER-2509>] -
   Unable to add Sequences into AM through Management Console
   - [APIMANAGER-2510 <https://wso2.org/jira/browse/APIMANAGER-2510>] -
   Added Sequences don't show up in the Add API Wizard
   - [APIMANAGER-2512 <https://wso2.org/jira/browse/APIMANAGER-2512>] -
   Sample README outdated
   - [APIMANAGER-2515 <https://wso2.org/jira/browse/APIMANAGER-2515>] -
   Reply text area is visible even when the users are not signed in.
   - [APIMANAGER-2516 <https://wso2.org/jira/browse/APIMANAGER-2516>] - API
   Docs UI issues
   - [APIMANAGER-2517 <https://wso2.org/jira/browse/APIMANAGER-2517>] -
   [API Store] "APIs" page is broken when "DisplayAllAPIs" is enabled
   - [APIMANAGER-2518 <https://wso2.org/jira/browse/APIMANAGER-2518>] -
   Error 500 when clicking on All Statistics link from Statistics page
   - [APIMANAGER-2519 <https://wso2.org/jira/browse/APIMANAGER-2519>] -
   Typo in Store Statistics Page
   - [APIMANAGER-2520 <https://wso2.org/jira/browse/APIMANAGER-2520>] - API
   Console embedded testing hangs
   - [APIMANAGER-2524 <https://wso2.org/jira/browse/APIMANAGER-2524>] -
   Missing upgrade script for Oracle database 1.6.0 -> 1.70
   - [APIMANAGER-2526 <https://wso2.org/jira/browse/APIMANAGER-2526>] -
   Admin Dashboard crashes when approving the last task of each page (when
   pagination is available)
   - [APIMANAGER-2528 <https://wso2.org/jira/browse/APIMANAGER-2528>] -
   Cannot create APIs with wsdl2
   - [APIMANAGER-2529 <https://wso2.org/jira/browse/APIMANAGER-2529>] -
   [Migration] APIM 1.6.0 to 1.7.0 migration does not work as expected
   - [APIMANAGER-2530 <https://wso2.org/jira/browse/APIMANAGER-2530>] -
   Issues with Migration scripts [mysql] - Data Migration 1.6.0 to 1.7.0
   - [APIMANAGER-2533 <https://wso2.org/jira/browse/APIMANAGER-2533>] -
   [Migration Issues] - Some information of migrated APIs are lost in edit mode
   - [APIMANAGER-2535 <https://wso2.org/jira/browse/APIMANAGER-2535>] -
   [Migration Issues] - Only the first HTTP verb is shown in migrated APIs.
   - [APIMANAGER-2536 <https://wso2.org/jira/browse/APIMANAGER-2536>] -
   AM_WORKFLOW table stores WF_UPDATED_TIME as "java.text.ParseException:
   Unparseable date: "<Error - Value '0000-00-00 00:00:00' can not be
   represented as java.sql.Timestamp>" for entries where WF_STATUS=CREATED
   - [APIMANAGER-2541 <https://wso2.org/jira/browse/APIMANAGER-2541>] - Can
   create multiple scopes with the same scope key and scope name, in the same
   - [APIMANAGER-2546 <https://wso2.org/jira/browse/APIMANAGER-2546>] -
   Cannot set "*" value in <Access-Control-Allow-Origin> under
   <CORSConfiguration> of api-manager.xml
   - [APIMANAGER-2548 <https://wso2.org/jira/browse/APIMANAGER-2548>] -
   When updating the docs,if the doc type change,that change is not preserving
   - [APIMANAGER-2549 <https://wso2.org/jira/browse/APIMANAGER-2549>] - Why
   AM add redundant prefix before the real endpoint address
   - [APIMANAGER-2550 <https://wso2.org/jira/browse/APIMANAGER-2550>] -
   Subscription page not loaded when there are large no of APIS for the same
   - [APIMANAGER-2551 <https://wso2.org/jira/browse/APIMANAGER-2551>] -
   Validation information cache at gateway side should be validate for each
   - [APIMANAGER-2554 <https://wso2.org/jira/browse/APIMANAGER-2554>] -
   Parts of the response is not proper JSON.
   - [APIMANAGER-2555 <https://wso2.org/jira/browse/APIMANAGER-2555>] -
   Make recently added APIs cache configurable.
   - [APIMANAGER-2558 <https://wso2.org/jira/browse/APIMANAGER-2558>] -
   When AM 1.6.0 migrate to 1.7.0,API document search not working to 1.6.0
   uploaded docs
   - [APIMANAGER-2559 <https://wso2.org/jira/browse/APIMANAGER-2559>] -
   Issues with swagger migration client from AM 1.6.0 to 1.7.0
   - [APIMANAGER-2561 <https://wso2.org/jira/browse/APIMANAGER-2561>] -
   log4j.properties file content includes incorrect references(of ESB).
   - [APIMANAGER-2564 <https://wso2.org/jira/browse/APIMANAGER-2564>] -
   When unicode characters are used for the application name, the key
   generation fails in chrome also when unicode used for api name api
   publication and subscription will fail
   - [APIMANAGER-2566 <https://wso2.org/jira/browse/APIMANAGER-2566>] - no
   Anonymous access to store when web sso enabled
   - [APIMANAGER-2567 <https://wso2.org/jira/browse/APIMANAGER-2567>] -
   User claims are not included in JWT token
   - [APIMANAGER-2568 <https://wso2.org/jira/browse/APIMANAGER-2568>] -
   Delete the scopes when deleting API
   - [APIMANAGER-2569 <https://wso2.org/jira/browse/APIMANAGER-2569>] -
   Composite primary keys mismatch in mysql tables and hive tables in stats
   - [APIMANAGER-2571 <https://wso2.org/jira/browse/APIMANAGER-2571>] -
   Oracle RAC script for AM database 1.7
   - [APIMANAGER-2573 <https://wso2.org/jira/browse/APIMANAGER-2573>] -
   Pizza Sample Update
   - [APIMANAGER-2574 <https://wso2.org/jira/browse/APIMANAGER-2574>] - NPE
   in ERROR - While trying to access API with email addresses as usernames
   - [APIMANAGER-2576 <https://wso2.org/jira/browse/APIMANAGER-2576>] -
   [Intermitten] When Implemeting an API, front end gives a dead page and
   backend throws an exception.
   - [APIMANAGER-2578 <https://wso2.org/jira/browse/APIMANAGER-2578>] - -
   Invalid token error is returned when a second API is added to an existing
   - [APIMANAGER-2580 <https://wso2.org/jira/browse/APIMANAGER-2580>] -
   Can't Create API
   - [APIMANAGER-2583 <https://wso2.org/jira/browse/APIMANAGER-2583>] -
   Forum HTML sanitizing issue
   - [APIMANAGER-2584 <https://wso2.org/jira/browse/APIMANAGER-2584>] - Not
   possible to delete tags at publisher
   - [APIMANAGER-2585 <https://wso2.org/jira/browse/APIMANAGER-2585>] -
   Refresh Token gives issue
   - [APIMANAGER-2586 <https://wso2.org/jira/browse/APIMANAGER-2586>] - Key
   cache validation fails
   - [APIMANAGER-2587 <https://wso2.org/jira/browse/APIMANAGER-2587>] - API
   Designer UI fixes
   - [APIMANAGER-2588 <https://wso2.org/jira/browse/APIMANAGER-2588>] -
   Postgress sql script is not working
   - [APIMANAGER-2589 <https://wso2.org/jira/browse/APIMANAGER-2589>] - AM
   apps SSO Single Logout is not working when fronted with AWSELB
   - [APIMANAGER-2594 <https://wso2.org/jira/browse/APIMANAGER-2594>] -
   "Endpoint Type" drop down content labels on API Add and API Edit pages are
   - [APIMANAGER-2595 <https://wso2.org/jira/browse/APIMANAGER-2595>] - GET
   request failed but the POST request succeeded using the same web service in
   API manager Store REST client Tool
   - [APIMANAGER-2596 <https://wso2.org/jira/browse/APIMANAGER-2596>] -
   Sequences list disappear if selected once
   - [APIMANAGER-2597 <https://wso2.org/jira/browse/APIMANAGER-2597>] -
   RemoveUserNameToJWTForApplicationToken set to true yeilds a Security
   - [APIMANAGER-2598 <https://wso2.org/jira/browse/APIMANAGER-2598>] -
   Getting errors when try to update the "secure service credentials" details
   on a created API
   - [APIMANAGER-2601 <https://wso2.org/jira/browse/APIMANAGER-2601>] -
   Server Start Time and the System Up Time calculated incorrectly
   - [APIMANAGER-2602 <https://wso2.org/jira/browse/APIMANAGER-2602>] -
   Unable to save APIs with WSDL endpoints when sandbox details are only
   - [APIMANAGER-2604 <https://wso2.org/jira/browse/APIMANAGER-2604>] - 'My
   Applications' page lists only 20 applications. No pagination is provided
   - [APIMANAGER-2605 <https://wso2.org/jira/browse/APIMANAGER-2605>] -
   Documents of an API are not copied when copying the API
   - [APIMANAGER-2606 <https://wso2.org/jira/browse/APIMANAGER-2606>] -
   Path parameter not accepted in API Manager
   - [APIMANAGER-2610 <https://wso2.org/jira/browse/APIMANAGER-2610>] -
   Indexing of .docx files failing
   - [APIMANAGER-2611 <https://wso2.org/jira/browse/APIMANAGER-2611>] -
   Production Endpoint is not properly validated at API creation
   - [APIMANAGER-2612 <https://wso2.org/jira/browse/APIMANAGER-2612>] -
   Documentataion links should be directed to 1.7.1
   - [APIMANAGER-2613 <https://wso2.org/jira/browse/APIMANAGER-2613>] -
   Business Owner & Technical Owner fields are missing in APIM 1.7.0
   - [APIMANAGER-2615 <https://wso2.org/jira/browse/APIMANAGER-2615>] -
   Once the access token is expired, cannot regenerate the access token in
   - [APIMANAGER-2616 <https://wso2.org/jira/browse/APIMANAGER-2616>] -
   Expired access tokens will be generated intermittently when you regenerate
   the access token for a particular application.
   - [APIMANAGER-2617 <https://wso2.org/jira/browse/APIMANAGER-2617>] - If
   http transport is disabled API WSDL URL would be empty in API edit UI
   - [APIMANAGER-2618 <https://wso2.org/jira/browse/APIMANAGER-2618>] - [P2
   repo] Relying part should not be added when installing key manager feature
   in Identity Server
   - [APIMANAGER-2619 <https://wso2.org/jira/browse/APIMANAGER-2619>] - Key
   cache validation failure on Key manager
   - [APIMANAGER-2621 <https://wso2.org/jira/browse/APIMANAGER-2621>] -
   Throws an error when loading my subscriptions after editing an application
   - [APIMANAGER-2622 <https://wso2.org/jira/browse/APIMANAGER-2622>] -
   Intermittent: Error is thrown when executing "Save and Publish" in Manage
   tab - APIM Store
   - [APIMANAGER-2623 <https://wso2.org/jira/browse/APIMANAGER-2623>] -
   Permissions of API definition document(swagger) are not set when copying
   the API
   - [APIMANAGER-2625 <https://wso2.org/jira/browse/APIMANAGER-2625>] - API
   Publisher/Store UI does not check session validity before initialized the
   - [APIMANAGER-2629 <https://wso2.org/jira/browse/APIMANAGER-2629>] - API
   Console doesn't work
   - [APIMANAGER-2630 <https://wso2.org/jira/browse/APIMANAGER-2630>] -
   Token Revocation doesn't work when with token encryption
   - [APIMANAGER-2631 <https://wso2.org/jira/browse/APIMANAGER-2631>] -
   Cannot generate tokens or invoke an API once the User Profile feature of IS
   5.0.0 is installed to APIM 1.7.1
   - [APIMANAGER-2632 <https://wso2.org/jira/browse/APIMANAGER-2632>] -
   Visibility Restriction to Roles feature does not work properly
   - [APIMANAGER-2634 <https://wso2.org/jira/browse/APIMANAGER-2634>] -
   README, release_notes.html files needs to be updated
   - [APIMANAGER-2640 <https://wso2.org/jira/browse/APIMANAGER-2640>] -
   Issues in Identity related PostgreSQL Scripts
   - [APIMANAGER-2642 <https://wso2.org/jira/browse/APIMANAGER-2642>] - NPE
   when invoking Authorize API [Cluster specific]
   - [APIMANAGER-2643 <https://wso2.org/jira/browse/APIMANAGER-2643>] - URL
   redirection issue for store signup
   - [APIMANAGER-2644 <https://wso2.org/jira/browse/APIMANAGER-2644>] -
   Application token generation time is not considered
   - [APIMANAGER-2645 <https://wso2.org/jira/browse/APIMANAGER-2645>] -
   There's a "/" appending to adding uri-templates from APIPublisher
   - [APIMANAGER-2646 <https://wso2.org/jira/browse/APIMANAGER-2646>] - API
   Manager Sharing API across multiple tenants does not work
   - [APIMANAGER-2647 <https://wso2.org/jira/browse/APIMANAGER-2647>] -
   Swagger try-it invocation fails when allowed methods are restrcited through
   the resource definition
   - [APIMANAGER-2648 <https://wso2.org/jira/browse/APIMANAGER-2648>] -
   Token regeneration fails when the AM server has a port offset
   - [APIMANAGER-2653 <https://wso2.org/jira/browse/APIMANAGER-2653>] - [AM
   stats] API_REQUEST_SUMMARY stat event ,apiPublisher has to be include
   username of API publisher
   - [APIMANAGER-2654 <https://wso2.org/jira/browse/APIMANAGER-2654>] - API
   resource editting related inconsistencies
   - [APIMANAGER-2657 <https://wso2.org/jira/browse/APIMANAGER-2657>] -
   Cannot copy APIs
   - [APIMANAGER-2658 <https://wso2.org/jira/browse/APIMANAGER-2658>] - Add
   the site.json requestURL parameter usage in AM doc
   - [APIMANAGER-2662 <https://wso2.org/jira/browse/APIMANAGER-2662>] -
   Migration: APIs published before cannot be invoked after the migration
   - [APIMANAGER-2663 <https://wso2.org/jira/browse/APIMANAGER-2663>] -
   Public API's made available to all tenant's not visible in anonymous mode
   (with registries mounted).
   - [APIMANAGER-2665 <https://wso2.org/jira/browse/APIMANAGER-2665>] - API
   Publisher/store traverse links appear when SSO is enabled regardless of the
   - [APIMANAGER-2666 <https://wso2.org/jira/browse/APIMANAGER-2666>] -
   When Logout from API store in 1.7.1, Backend gives an error
   - [APIMANAGER-2667 <https://wso2.org/jira/browse/APIMANAGER-2667>] - [IS
   as key manager] Cannot add SPs after installing key manager feature in IS
   - [APIMANAGER-2668 <https://wso2.org/jira/browse/APIMANAGER-2668>] -
   Error when trying to revert installed key manager feature from IS
   - [APIMANAGER-2669 <https://wso2.org/jira/browse/APIMANAGER-2669>] -
   [Migration] When AM 1.6.0 migrate to 1.7.0,Resources are not copied
   correctly in latest pack
   - [APIMANAGER-2670 <https://wso2.org/jira/browse/APIMANAGER-2670>] -
   Swagger UI based invocation failures
   - [APIMANAGER-2671 <https://wso2.org/jira/browse/APIMANAGER-2671>] -
   HTTP verbs ommited when adding resources
   - [APIMANAGER-2673 <https://wso2.org/jira/browse/APIMANAGER-2673>] -
   Unable to revoke the Token when Activity monitory enabled
   - [APIMANAGER-2675 <https://wso2.org/jira/browse/APIMANAGER-2675>] -
   Recently added API list is not updated with the most recent APIs
   - [APIMANAGER-2680 <https://wso2.org/jira/browse/APIMANAGER-2680>] -
   Empty response body for DELETE invocations when inline responses are
   specified instead of a backend service
   - [APIMANAGER-2682 <https://wso2.org/jira/browse/APIMANAGER-2682>] -
   Blank page displayed when inline script is empty
   - [APIMANAGER-2683 <https://wso2.org/jira/browse/APIMANAGER-2683>] -
   APIM generate new consumer-secrete key pair even IS has a pair of
   consumer-secrete keys.
   - [APIMANAGER-2684 <https://wso2.org/jira/browse/APIMANAGER-2684>] - API
   publishing is allowed when the inline script is uncommented
   - [APIMANAGER-2688 <https://wso2.org/jira/browse/APIMANAGER-2688>] -
   Forum topic search issue
   - [APIMANAGER-2690 <https://wso2.org/jira/browse/APIMANAGER-2690>] -
   Subscription availability option for specific tenants does not work for
   super tenant
   - [APIMANAGER-2698 <https://wso2.org/jira/browse/APIMANAGER-2698>] -
   Migration: Cannot create a new version of a migrated API
   - [APIMANAGER-2699 <https://wso2.org/jira/browse/APIMANAGER-2699>] -
   'Rejected' status is not properly handled in Subscription Creation workflow
   - [APIMANAGER-2701 <https://wso2.org/jira/browse/APIMANAGER-2701>] -
   Impact of Gateway resource caching
   - [APIMANAGER-2704 <https://wso2.org/jira/browse/APIMANAGER-2704>] -
   Blocked subscriptions can be unblocked by re-subscribing to an API
   - [APIMANAGER-2705 <https://wso2.org/jira/browse/APIMANAGER-2705>] -
   Exception when loading APIs on store for a tenant user from a secondary
   user store
   - [APIMANAGER-2708 <https://wso2.org/jira/browse/APIMANAGER-2708>] -
   EndPointURL log is null in APIManagerExtensionHandler
   - [APIMANAGER-2712 <https://wso2.org/jira/browse/APIMANAGER-2712>] -
   Multiple version are available under recently added APIs when multiple
   version display is disabled
   - [APIMANAGER-2713 <https://wso2.org/jira/browse/APIMANAGER-2713>] -
   Error when publishing API copies without the option 'require re-subscription
   - [APIMANAGER-2714 <https://wso2.org/jira/browse/APIMANAGER-2714>] -
   Auto subscription of does not work for new versions of
   deprecated/retired/blocked APIs
   - [APIMANAGER-2719 <https://wso2.org/jira/browse/APIMANAGER-2719>] -
   Default versions of APIs can be invoked without subscription
   - [APIMANAGER-2720 <https://wso2.org/jira/browse/APIMANAGER-2720>] -
   Custom sequences cannot be removed once the API is saved
   - [APIMANAGER-2721 <https://wso2.org/jira/browse/APIMANAGER-2721>] -
   Custom sequences dissappear when the option is enabled/disabled
   - [APIMANAGER-2729 <https://wso2.org/jira/browse/APIMANAGER-2729>] -
   cipher-text.properties & cipher-tool.properties files are missing in AM1.7.1
   - [APIMANAGER-2731 <https://wso2.org/jira/browse/APIMANAGER-2731>] -
   Gateway cache is not invalidated on token revokation
   - [APIMANAGER-2732 <https://wso2.org/jira/browse/APIMANAGER-2732>] -
   Tiers cannot be removed once added
   - [APIMANAGER-2733 <https://wso2.org/jira/browse/APIMANAGER-2733>] -
   Store statistics are not updated when token encryption is enabled
   - [APIMANAGER-2734 <https://wso2.org/jira/browse/APIMANAGER-2734>] -
   When a user attempts to create an api on clicking implementation an
   exception is thrown
   - [APIMANAGER-2735 <https://wso2.org/jira/browse/APIMANAGER-2735>] -
   Modifications to migration tool readme in migration-1.6.0_to_1.7.0
   - [APIMANAGER-2736 <https://wso2.org/jira/browse/APIMANAGER-2736>] -
   Token regeneration error for an api migrated from 1.6 to 1.7 using H2 DB
   - [APIMANAGER-2738 <https://wso2.org/jira/browse/APIMANAGER-2738>] - IS
   as Key Manager failure in APIM1.7.1
   - [APIMANAGER-2739 <https://wso2.org/jira/browse/APIMANAGER-2739>] -
   when unlimited tier permissions are denied for a role thenon subscription
   page no tiers are listed but on application creation page the tiers are
   - [APIMANAGER-2740 <https://wso2.org/jira/browse/APIMANAGER-2740>] - An
   API which was copied from another shows subscriptions as 100%
   - [APIMANAGER-2741 <https://wso2.org/jira/browse/APIMANAGER-2741>] -
   Tier of a deleted application is assigned to new applications with the same
   - [APIMANAGER-2742 <https://wso2.org/jira/browse/APIMANAGER-2742>] -
   Tier level mix up when adding/deleting applications
   - [APIMANAGER-2743 <https://wso2.org/jira/browse/APIMANAGER-2743>] -
   Application throttling tier changes are not immediately applied when
   gateway cache is enabled
   - [APIMANAGER-2744 <https://wso2.org/jira/browse/APIMANAGER-2744>] -
   Incorrect user registration date/times under active subscriptions of an API
   - [APIMANAGER-2746 <https://wso2.org/jira/browse/APIMANAGER-2746>] -
   Cannot copy API's with documents
   - [APIMANAGER-2750 <https://wso2.org/jira/browse/APIMANAGER-2750>] -
   Multiple subscription entries for an API for the same user and application
   observed intermittently
   - [APIMANAGER-2751 <https://wso2.org/jira/browse/APIMANAGER-2751>] -
   Tier levels once assigned to an API cannot be removed
   - [APIMANAGER-2754 <https://wso2.org/jira/browse/APIMANAGER-2754>] - UI
   Issues of WSO2 API Manager
   - [APIMANAGER-2757 <https://wso2.org/jira/browse/APIMANAGER-2757>] -
   Error when executing APIPopulator.sh for YouTubeFeeds sample
   - [APIMANAGER-2758 <https://wso2.org/jira/browse/APIMANAGER-2758>] -
   Publisher and Store having problems with IE9 on Windows 7
   - [APIMANAGER-2759 <https://wso2.org/jira/browse/APIMANAGER-2759>] -
   Pizzashack sample image loading issue
   - [APIMANAGER-2762 <https://wso2.org/jira/browse/APIMANAGER-2762>] -
   Billing Data sample does not work as expected
   - [APIMANAGER-2763 <https://wso2.org/jira/browse/APIMANAGER-2763>] -
   [Intermittent] on some occasions when an api is created Caused by:
   org.apache.axis2.AxisFault: Exception occurred while trying to invoke
   service method addApiFromString is thrown on the back end
   - [APIMANAGER-2764 <https://wso2.org/jira/browse/APIMANAGER-2764>] - NPE
   when invoking admin services
   - [APIMANAGER-2765 <https://wso2.org/jira/browse/APIMANAGER-2765>] -
   addDocumentation API in the Publisher response with error:false even after
   an error on the Back-End
   - [APIMANAGER-2766 <https://wso2.org/jira/browse/APIMANAGER-2766>] -
   Design API UI issue
   - [APIMANAGER-2767 <https://wso2.org/jira/browse/APIMANAGER-2767>] -
   domain restriction seems to be broken
   - [APIMANAGER-2770 <https://wso2.org/jira/browse/APIMANAGER-2770>] - on
   cluster setup the responses for api invokes via API Console does not work
   - [APIMANAGER-2776 <https://wso2.org/jira/browse/APIMANAGER-2776>] -
   Rampart client module not available in APIM
   - [APIMANAGER-2778 <https://wso2.org/jira/browse/APIMANAGER-2778>] -
   Incorrect capitalization in Visibility options
   - [APIMANAGER-2779 <https://wso2.org/jira/browse/APIMANAGER-2779>] -
   Bundle Activation Fails when api-manager.xml has invalid xml content
   - [APIMANAGER-2781 <https://wso2.org/jira/browse/APIMANAGER-2781>] -
   Cannot remove tiers from a freshly created API
   - [APIMANAGER-2782 <https://wso2.org/jira/browse/APIMANAGER-2782>] -
   Error while listing subscriptions in UI after deleting one
   subscription(selected) from rest API call(using curl)
   - [APIMANAGER-2797 <https://wso2.org/jira/browse/APIMANAGER-2797>] -
   [Failover endpoint] Not getting directed to the fail over endpoint when the
   prodcution endpoint is down
   - [APIMANAGER-2799 <https://wso2.org/jira/browse/APIMANAGER-2799>] -
   Migration: Migration does not work
   - [APIMANAGER-2800 <https://wso2.org/jira/browse/APIMANAGER-2800>] -
   Intermittent error on AM management console logout (SSO)
   - [APIMANAGER-2801 <https://wso2.org/jira/browse/APIMANAGER-2801>] -
   [intermitant] "Exception occurred while trying to invoke service method
   addApiFromString" is thrown when adding an API with advance options
   selected for endpoints
   - [APIMANAGER-2803 <https://wso2.org/jira/browse/APIMANAGER-2803>] - key
   manager seems to generates the same 2 tokens all the time
   - [APIMANAGER-2804 <https://wso2.org/jira/browse/APIMANAGER-2804>] -
   [Store] Issues in recently added section
   - [APIMANAGER-2806 <https://wso2.org/jira/browse/APIMANAGER-2806>] -
   Cross domain request fail when inline js implementation added as endpoint
   - [APIMANAGER-2811 <https://wso2.org/jira/browse/APIMANAGER-2811>] -
   when an API does not have response caching enabled when invoking a load
   balancer end point based API if the end points go down the APIM has to be
   restarted for successful invocation of the curl command
   - [APIMANAGER-2812 <https://wso2.org/jira/browse/APIMANAGER-2812>] - The
   workflow admin application creation page does not get updated if the
   application was deleted prior to approval
   - [APIMANAGER-2814 <https://wso2.org/jira/browse/APIMANAGER-2814>] -
   when application registration flow is not used even though a subscription
   request was rejected from admin console the users are allowed to invoke
   access tokens
   - [APIMANAGER-2815 <https://wso2.org/jira/browse/APIMANAGER-2815>] -
   startup of the APIM does not show the link for admin dashboard
   - [APIMANAGER-2816 <https://wso2.org/jira/browse/APIMANAGER-2816>] -
   registration of users to store is not provided for tenant domain
   - [APIMANAGER-2817 <https://wso2.org/jira/browse/APIMANAGER-2817>] -
   when a tenant admin logs in and access the admin dashboard errors are
   generated and request does not come for authorization
   - [APIMANAGER-2828 <https://wso2.org/jira/browse/APIMANAGER-2828>] -
   [intermittent] on some occasions when signing out of API store an error
   page is generated
   - [APIMANAGER-2829 <https://wso2.org/jira/browse/APIMANAGER-2829>] -
   Admin users in the carbon.super domain seems to get approval request for
   workflow of another tenant
   - [APIMANAGER-2830 <https://wso2.org/jira/browse/APIMANAGER-2830>] -
   HTTP DELETE not working with DISABLE_CHUNKING option
   - [APIMANAGER-2832 <https://wso2.org/jira/browse/APIMANAGER-2832>] -
   Admin dashboard - Approval status dropdown issue
   - [APIMANAGER-2834 <https://wso2.org/jira/browse/APIMANAGER-2834>] -
   Cannot invoke a prototyped API using the API console
   - [APIMANAGER-2839 <https://wso2.org/jira/browse/APIMANAGER-2839>] - if
   two publisher access the same API and one deletes and other views then the
   viewer is shown a dead page
   - [APIMANAGER-2840 <https://wso2.org/jira/browse/APIMANAGER-2840>] -
   [Distributed setup] Observed an NPE when trying to generate token
   - [APIMANAGER-2842 <https://wso2.org/jira/browse/APIMANAGER-2842>] - if
   two publishers are updating the same API then the user who deletes a scope
   record may see that record still existing
   - [APIMANAGER-2844 <https://wso2.org/jira/browse/APIMANAGER-2844>] -
   [Distributed setup] Error when generating token if there's no connection
   made to key manager from publisher node
   - [APIMANAGER-2845 <https://wso2.org/jira/browse/APIMANAGER-2845>] -
   Error while accessing an api in store
   - [APIMANAGER-2847 <https://wso2.org/jira/browse/APIMANAGER-2847>] -
   system does not inform why a publisher role user without create permisison
   cant edit an API
   - [APIMANAGER-2849 <https://wso2.org/jira/browse/APIMANAGER-2849>] -
   Popup error message for document creating errors
   - [APIMANAGER-2850 <https://wso2.org/jira/browse/APIMANAGER-2850>] -
   WorkFlows: When the default user is changed, workflows does not work
   - [APIMANAGER-2856 <https://wso2.org/jira/browse/APIMANAGER-2856>] - OOM
   exception crashed the gateway/keymanager node while doing various operations
   - [APIMANAGER-2857 <https://wso2.org/jira/browse/APIMANAGER-2857>] -
   redirector.jag redirects the user to https without honouring proxy port
   when prompting the user to login in store
   - [APIMANAGER-2858 <https://wso2.org/jira/browse/APIMANAGER-2858>] -
   Error when accessing the store
   - [APIMANAGER-2860 <https://wso2.org/jira/browse/APIMANAGER-2860>] -
   Error while accessing an published api in store
   - [APIMANAGER-2863 <https://wso2.org/jira/browse/APIMANAGER-2863>] -
   Server start fails after few server restarts
   - [APIMANAGER-2864 <https://wso2.org/jira/browse/APIMANAGER-2864>] - Why
   can't we rollback API creation when an issue occurs while publishing the
   - [APIMANAGER-2865 <https://wso2.org/jira/browse/APIMANAGER-2865>] -
   am_stats_analyzer script packaged in API_Manager_Analytics.tbox with API
   Manager 1.7 has a typo in one of the queries
   - [APIMANAGER-2868 <https://wso2.org/jira/browse/APIMANAGER-2868>] -
   mode parameter should validate
   - [APIMANAGER-2870 <https://wso2.org/jira/browse/APIMANAGER-2870>] -
   'APIs By Provider - Administrator' - Search for users is broken
   - [APIMANAGER-2871 <https://wso2.org/jira/browse/APIMANAGER-2871>] - API
   resources lost after restarting the Publisher node if default resource is
   set while creating an API
   - [APIMANAGER-2873 <https://wso2.org/jira/browse/APIMANAGER-2873>] -
   Carbon.xml version should be changed to 1.8.0
   - [APIMANAGER-2875 <https://wso2.org/jira/browse/APIMANAGER-2875>] - API
   Manager 1.8.0: Release docs should be updated
   - [APIMANAGER-2876 <https://wso2.org/jira/browse/APIMANAGER-2876>] -
   User sign up icon is not visible in store
   - [APIMANAGER-2877 <https://wso2.org/jira/browse/APIMANAGER-2877>] -
   Complete resource path should delete with API delete
   - [APIMANAGER-2879 <https://wso2.org/jira/browse/APIMANAGER-2879>] -
   When accessing the freshly created APIs from the Store node, User
   wso2.anonymous.user is not authorized to read the resource
   was thrown
   - [APIMANAGER-2883 <https://wso2.org/jira/browse/APIMANAGER-2883>] -
   Store crashes when loading a visibility restricted API
   - [APIMANAGER-2884 <https://wso2.org/jira/browse/APIMANAGER-2884>] -
   Cannot use a newly created role as the parameter for "Visible to Roles"
   when the visibility is set as "Restricted by roles""
   - [APIMANAGER-2887 <https://wso2.org/jira/browse/APIMANAGER-2887>] -
   [Store] SQLIntegrityConstraintViolationException when accessing the store
   for the first time and then did not observe this error
   - [APIMANAGER-2888 <https://wso2.org/jira/browse/APIMANAGER-2888>] -
   Image does not appear in recently added section
   - [APIMANAGER-2889 <https://wso2.org/jira/browse/APIMANAGER-2889>] - the
   module that creates API scopes need to show mandatory fields and validate
   for data when creating
   - [APIMANAGER-2891 <https://wso2.org/jira/browse/APIMANAGER-2891>] -
   Error on API Manager 1.8 with Resource level Authentication"Application
   - [APIMANAGER-2893 <https://wso2.org/jira/browse/APIMANAGER-2893>] -
   Store UI doesn't display appropriate error for invalid search queries
   - [APIMANAGER-2894 <https://wso2.org/jira/browse/APIMANAGER-2894>] -
   Transport selection is not working as expected in publisherUI
   - [APIMANAGER-2895 <https://wso2.org/jira/browse/APIMANAGER-2895>] -
   publisher module does not validate if the user role given within the scope
   is existent within the user store
   - [APIMANAGER-2896 <https://wso2.org/jira/browse/APIMANAGER-2896>] -
   When a timeout happen in publisher/store app with SSO enabled,it directs to
   a login popup box instead the SSO login Page
   - [APIMANAGER-2897 <https://wso2.org/jira/browse/APIMANAGER-2897>] -
   Tenant Axis configuration is not created when login to the Publisher and
   Store when SSO is enabled
   - [APIMANAGER-2900 <https://wso2.org/jira/browse/APIMANAGER-2900>] -
   [Store] [Tenant] Observed WARN
   {org.wso2.carbon.registry.indexing.ResourceSubmitter} - An error occurred
   while submitting the resource for indexing, path:
   {org.wso2.carbon.registry.indexing.ResourceSubmitter} in store
   - [APIMANAGER-2901 <https://wso2.org/jira/browse/APIMANAGER-2901>] -
   [Intermittentissue] when publishing API
   - [APIMANAGER-2902 <https://wso2.org/jira/browse/APIMANAGER-2902>] -
   Request sent to GW fails with java.lang.RuntimeException: Cannot create
   tenant ConfigurationContext for tenant sanuthi4.com
   - [APIMANAGER-2911 <https://wso2.org/jira/browse/APIMANAGER-2911>] -
   even though API manager was started with -Dprofile=api-publisher i was able
   to login to API store and generate access tokens in API store
   - [APIMANAGER-2913 <https://wso2.org/jira/browse/APIMANAGER-2913>] -
   Remove build sequence from the axis configuration
   - [APIMANAGER-2914 <https://wso2.org/jira/browse/APIMANAGER-2914>] - API
   doesn't get published to Store, when published using lifecycle
   - [APIMANAGER-2915 <https://wso2.org/jira/browse/APIMANAGER-2915>] -
   Endpoint UI I18n issue at Publisher webapp
   - [APIMANAGER-2916 <https://wso2.org/jira/browse/APIMANAGER-2916>] -
   [Store] com.hazelcast.nio.serialization.HazelcastSerializationException
   error observed in store logs
   - [APIMANAGER-2917 <https://wso2.org/jira/browse/APIMANAGER-2917>] -
   [intermittent] on some occasions when an API is created and published the
   attached exception is thrown
   - [APIMANAGER-2919 <https://wso2.org/jira/browse/APIMANAGER-2919>] -
   Single Logout does not work between webapps (fronted by WSO2 ELB)
   - [APIMANAGER-2920 <https://wso2.org/jira/browse/APIMANAGER-2920>] -
   Remove Edit link for 'publish' only users
   - [APIMANAGER-2921 <https://wso2.org/jira/browse/APIMANAGER-2921>] -
   Token Response Capitalization
   - [APIMANAGER-2926 <https://wso2.org/jira/browse/APIMANAGER-2926>] -
   APIM - BPS SubscriptionApproval workflow not working
   - [APIMANAGER-2929 <https://wso2.org/jira/browse/APIMANAGER-2929>] - Add
   headers to stop gateway from sending OPTIONS calls to the back end
   - [APIMANAGER-2931 <https://wso2.org/jira/browse/APIMANAGER-2931>] -
   [Intermittent issue] EmptyStackException when ending tenant flow when SSO
   is enabled
   - [APIMANAGER-2932 <https://wso2.org/jira/browse/APIMANAGER-2932>] -
   Getting Errors when trying to create tenants on APIM which pointed to a
   PostgreSQL database
   - [APIMANAGER-2933 <https://wso2.org/jira/browse/APIMANAGER-2933>] -
   Sequence edit view is selected by default if there is no any sequences.
   - [APIMANAGER-2934 <https://wso2.org/jira/browse/APIMANAGER-2934>] - API
   Store is not properly handling expired session when SSO is enabled
   - [APIMANAGER-2936 <https://wso2.org/jira/browse/APIMANAGER-2936>] -
   Error occurs while trying to update docs in publisher
   - [APIMANAGER-2940 <https://wso2.org/jira/browse/APIMANAGER-2940>] -
   Inline endpoint does not work
   - [APIMANAGER-2948 <https://wso2.org/jira/browse/APIMANAGER-2948>] -
   [Tenant Mode] Once an API is deleted, cannot add another with the same name
   until cache expires
   - [APIMANAGER-2949 <https://wso2.org/jira/browse/APIMANAGER-2949>] - An
   error popup is visible while redirecting to SSO login page after a session
   timeout in APIM store
   - [APIMANAGER-2950 <https://wso2.org/jira/browse/APIMANAGER-2950>] -
   [Migration Issues] Interactive documentation of the API is missing in the
   API console after migrating from APIM 1.7 to APIM 1.8
   - [APIMANAGER-2951 <https://wso2.org/jira/browse/APIMANAGER-2951>] -
   Application developer cannot invoke APIs when the API resource level set to
   'Application User'
   - [APIMANAGER-2965 <https://wso2.org/jira/browse/APIMANAGER-2965>] -
   Application Name showed as null in all store statistics pages when token
   encryption enabled
   - [APIMANAGER-2970 <https://wso2.org/jira/browse/APIMANAGER-2970>] -
   Save and Publish button enabled for creator only role
   - [APIMANAGER-2973 <https://wso2.org/jira/browse/APIMANAGER-2973>] - BAM
   configuration error in Publisher / API / Versions
   - [APIMANAGER-2975 <https://wso2.org/jira/browse/APIMANAGER-2975>] -
   Error while a new user trying to sign up to the Store - Though the user
   gets added
   - [APIMANAGER-2976 <https://wso2.org/jira/browse/APIMANAGER-2976>] -
   Navigation gets blocked in the Publisher for a user created inside a
   tenant, after adding a document with the visibility state 'Private'
   - [APIMANAGER-2979 <https://wso2.org/jira/browse/APIMANAGER-2979>] -
   Regenerate Access Token fails in the Store and Keymanager separated cluster
   - [APIMANAGER-2981 <https://wso2.org/jira/browse/APIMANAGER-2981>] -
   Erroneous DB scripts - Some of the tables don't get created
   - [APIMANAGER-2983 <https://wso2.org/jira/browse/APIMANAGER-2983>] -
   Workflows: Application Registration and Subscription are returning 404
   unauthorized in BPS
   - [APIMANAGER-2984 <https://wso2.org/jira/browse/APIMANAGER-2984>] -
   HTTP endpoint does not allow dot between path seperators
   - [APIMANAGER-2985 <https://wso2.org/jira/browse/APIMANAGER-2985>] -
   There should be separate service and port fields for Production WSDL and
   Sandbox WSDL
   - [APIMANAGER-2986 <https://wso2.org/jira/browse/APIMANAGER-2986>] - If
   you invoke /token with bad credentials, the carbon home page contents are
   - [APIMANAGER-2987 <https://wso2.org/jira/browse/APIMANAGER-2987>] -
   Store logout does not redirect to the logged out screen until a browser
   cache refresh
   - [APIMANAGER-2988 <https://wso2.org/jira/browse/APIMANAGER-2988>] -
   Tenant API store is broken
   - [APIMANAGER-2990 <https://wso2.org/jira/browse/APIMANAGER-2990>] -
   Remove "Save & Publish" button and "Deploy as a prototype" button for API
   creators who don't have 'publish' permissions
   - [APIMANAGER-2991 <https://wso2.org/jira/browse/APIMANAGER-2991>] -
   Error when adding .docx files to an API
   - [APIMANAGER-2996 <https://wso2.org/jira/browse/APIMANAGER-2996>] - In
   an authentication failure, request payload is returned as the response
   - [APIMANAGER-2997 <https://wso2.org/jira/browse/APIMANAGER-2997>] -
   Workflows: Can't invoke an api which was previously rejected and
   - [APIMANAGER-3012 <https://wso2.org/jira/browse/APIMANAGER-3012>] -
   java.lang.NullPointerException thrown when invoking an API on a clustered
   - [APIMANAGER-3013 <https://wso2.org/jira/browse/APIMANAGER-3013>] -
   APIs suddenly disappeared from the publisher after a small volume test
   - [APIMANAGER-3019 <https://wso2.org/jira/browse/APIMANAGER-3019>] -
   Publisher login attempt will give a hazelcast exception in the key manager
   - [APIMANAGER-3020 <https://wso2.org/jira/browse/APIMANAGER-3020>] -
   Invalid publisher name is displayed in "More APIs from Provider" Area
   - [APIMANAGER-3021 <https://wso2.org/jira/browse/APIMANAGER-3021>] - Fix
   syntax error in AM_WORKFLOWS table of oracle.sql
   - [APIMANAGER-3027 <https://wso2.org/jira/browse/APIMANAGER-3027>] -
   Sandbox field became blank in the Store UI
   - [APIMANAGER-3028 <https://wso2.org/jira/browse/APIMANAGER-3028>] -
   Regenerate option in the Store UI will revoke the existing access token,
   but still shows the same token in the UI. API invocations with the revoked
   token will be successful and unsuccessful through random gatetway nodes
   - [APIMANAGER-3034 <https://wso2.org/jira/browse/APIMANAGER-3034>] - In
   the API Implementation stage, the Endpoint Test gives Invalid message even
   for working endpoints
   - [APIMANAGER-3042 <https://wso2.org/jira/browse/APIMANAGER-3042>] -
   Invalid error codes returned for API invocations when tokens are
   - [APIMANAGER-3046 <https://wso2.org/jira/browse/APIMANAGER-3046>] - If
   Key Manager i.e.; IS, is not responding at the time of creating a new
   application key, key generation fails and the Application becomes unusable
   - [APIMANAGER-3047 <https://wso2.org/jira/browse/APIMANAGER-3047>] -
   Publisher node (turned up in publisher profile) tries to call a Keymanager
   service endpoint; while trying to update an API; and fails. Issue
   explicitly occurs when GatewayKeyCache and KeyMgtValidationInfoCache both
   are disabled in the publisher node

Patches for previous release version

   - [APIMANAGER-2241 <https://wso2.org/jira/browse/APIMANAGER-2241>] -
   ConcurrentModificationException at server startup
   - [APIMANAGER-2532 <https://wso2.org/jira/browse/APIMANAGER-2532>] -
   APIM store performance improvements
   - [APIMANAGER-2590 <https://wso2.org/jira/browse/APIMANAGER-2590>] -
   Response body is getting dropped occasionally after timeout is triggered
   from TimeoutHandler
   - [APIMANAGER-2592 <https://wso2.org/jira/browse/APIMANAGER-2592>] -
   APIM store shows internal IP when run behind the Nginx and resources are
   not properly shown
   - [APIMANAGER-2627 <https://wso2.org/jira/browse/APIMANAGER-2627>] -
   Cannot invoke when we invoke API with context with multiple back slashes
   - [APIMANAGER-2700 <https://wso2.org/jira/browse/APIMANAGER-2700>] -
   EndPointURL is logged as null from APIManagerExtensionHandler
   - [APIMANAGER-2706 <https://wso2.org/jira/browse/APIMANAGER-2706>] - API
   delete leaves some traces of it.
   - [APIMANAGER-2752 <https://wso2.org/jira/browse/APIMANAGER-2752>] - Add
   debug level logs API Manager 1.6.0

All resolved issues

   - WSO2 API Manager 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
      - 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
      - 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 the API lifecycle (publish, deprecate, retire).
      - Attach documentation (files, external URLs) to APIs.
      - Apply Security policies to APIs (authentication, authorization).
      - Associate API available to system defined service tiers.
      - Provision and Manage API keys.
      - Track consumers per API.
      - One-click deployment to API Gateway for immediate publishing.
   - Route API Traffic:
      - Supports API authentication with OAuth2.
      - Extremely high performance pass-through message routing with
      sub-millisecond latency.
      - Enforce rate limiting and throttling policies for APIs by consumer.
      - Horizontally scalable with easy deployment into cluster using
      proven routing infrastructure.
      - Scales to millions of developers/users.
      - Capture all statistics and push to pluggable analytics system.
      - Configure API routing policies with capabilities of WSO2 Enterprise
      Service Bus.
      - Powered by WSO2 Enterprise Service Bus.
   - Manage Developer Community:
      - Self-sign up for API consumption.
      - Manage user account including password reset.
      - Developer interaction with APIs via comments and ratings.
      - Support for developer communication via forums (Available soon in
      future version).
      - Powered by WSO2 Identity Server.
   - Govern Complete API Lifecycle:
      - Manage API lifecycle from cradle to grave: create, publish, block,
      deprecate and retire.
      - Publish both production and sandbox keys for APIs to enable easy
      developer testing.
      - Publish APIs to partner networks such as ProgrammableWeb (Available
      soon in future version).
      - Powered by WSO2 Governance Registry.
   - Monitor API Usage and Performance:
      - All API usage published to pluggable analytics framework.
      - Out of the box support for WSO2 Business Activity Monitor and
      Google Analytics.
      - View metrics by user, API and more.
      - Customized reporting via plugging reporting engines.
      - Monitor SLA compliance.
      - Powered by WSO2 Business Activity Monitor.
   - Pluggable, Extensible and Themeable:
      - All components are highly customizable thru styling, theming and
      open source code.
      - Storefront implemented with Jaggery (jaggeryjs.org) for easy
      - Pluggable to third party analytics systems and billing systems
      (Available soon in future version).
      - Pluggable to existing user stores including via JDBC and LDAP.
      - Components usable separately - storefront can be used to front APIs
      gatewayed via third party gateways such as Intel Expressway
Service Gateway.
      - Support for Single Sign On (SSO) using SAML 2.0 for easy
      integration with existing web apps
   - Easily Deployable in Enterprise Setting:
      - Role based access control for managing users and their
      authorization levels.
      - Store front can be deployed in DMZ for external access with
      Publisher inside the firewall for private control.
      - Different user stores for developer focused store-front and
      internal operations in publisher.
      - Integrates with enterprise identity systems including LDAP and
      Microsoft Active Directory.
      - Gateway can be deployed in DMZ with controlled access to WSO2
      Identity Server (for authentication/authorization) and
governance database
      behind firewall.
   - Support for creating multi-tenanted APIs
      - Run a single instance and provide API Management to multiple
      - Share APIs between different departments in a large enterprise
   - Publishing and Governing API Use
      - Document an API using Swagger
      - Restrict API Access tokens to domains/IPs
      - Ability to block a subscription and restricting a complete
      - Ability to revoke access tokens
      - Separate validity period configuration for Application Access Token
      - OAuth2 Authorization Code Grant Type Support
      - Configuring execution point of mediation extensions
   - Monitor API Usage and Performance
      - Improved dashboard for monitoring usage statistics (Filtering data
      for a date range, More visually appealing widgets)

Known Issues

All the open issues pertaining to WSO2 API Manager are reported at the
following location:

   - Known Issues

How You Can ContributeMailing Lists

Join our mailing list and correspond with the developers directly.

   - Developer List : dev at wso2.org | Subscribe
   <dev-request at wso2.org?subject=subscribe> | Mail Archive
   - User List : user at wso2.org | Subscribe
   <user-request at wso2.org?subject=subscribe> | Mail Archive

Reporting Issues

We encourage you to report issues, documentation faults and feature
requests regarding WSO2 API Manager through the public API Manager JIRA
<https://wso2.org/jira/browse/APIMANAGER>. You can use the Carbon JIRA
<http://www.wso2.org/jira/browse/CARBON> to report any issues related to
the Carbon base framework or associated Carbon components.

We are committed to ensuring that your enterprise middleware deployment is
completely supported from evaluation to production. Our unique approach
ensures that all support leverages our open development methodology and is
provided by the very same engineers who build the technology.

For more details and to take advantage of this unique opportunity please
visit http://wso2.com/support.

To learn more about WSO2 API Manager and WSO2 support offerings please
visit http://wso2.com/products/api-manager.

*-- The WSO2 API Manager Team --*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.wso2.org/pipermail/announce/attachments/20141216/01395bc9/attachment-0001.html>

More information about the Announce mailing list