WSO2 API Manager 1.3.0 Released! WSO2 API Manager team is pleased to announce the release of version 1.3.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 - *Key Manager* : Key Management services on top of WSO2 IS It 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. Online documentation<http://docs.wso2.org/wiki/display/AM130/WSO2+API+Manager+Documentation>is also available. 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/publisherto access the API provider webapp 5. Navigate to https://localhost:9443/store to access the API store 6. Use "admin", "admin" as the username and password to login as an admin (For demo only. Please refer user guide on how to create proper user accounts) New Features of WSO2 API Manager 1.3.0 This release of API Manager comes with a horde of new features and bug fixes. New Features - [APIMANAGER-774 <https://wso2.org/jira/browse/APIMANAGER-774>] - PostgreSQL as a back end - [APIMANAGER-814 <https://wso2.org/jira/browse/APIMANAGER-814>] - i18n Support - [APIMANAGER-839 <https://wso2.org/jira/browse/APIMANAGER-839>] - Implement specifying Authentication Scheme at resources level - [APIMANAGER-845 <https://wso2.org/jira/browse/APIMANAGER-845>] - Integration with Google Analytics as alternative to BAM for API Gateway - [APIMANAGER-849 <https://wso2.org/jira/browse/APIMANAGER-849>] - More graphs/widgets on error statistics - [APIMANAGER-851 <https://wso2.org/jira/browse/APIMANAGER-851>] - Built-in REST client in API Store - [APIMANAGER-852 <https://wso2.org/jira/browse/APIMANAGER-852>] - Access token revoke functionality - [APIMANAGER-853 <https://wso2.org/jira/browse/APIMANAGER-853>] - Improved Self registration Process - [APIMANAGER-862 <https://wso2.org/jira/browse/APIMANAGER-862>] - Support for connecting to secured back end services - [APIMANAGER-868 <https://wso2.org/jira/browse/APIMANAGER-868>] - Application Level throttling - [APIMANAGER-871 <https://wso2.org/jira/browse/APIMANAGER-871>] - Public / Private APIs - [APIMANAGER-911 <https://wso2.org/jira/browse/APIMANAGER-911>] - Access token storage partitioning with multiple user stores - [APIMANAGER-913 <https://wso2.org/jira/browse/APIMANAGER-913>] - Workflow extension support for API Store self sign up process - [APIMANAGER-914 <https://wso2.org/jira/browse/APIMANAGER-914>] - Sample Billing data generation - [APIMANAGER-915 <https://wso2.org/jira/browse/APIMANAGER-915>] - Improved search options for API search and Access Token search - [APIMANAGER-925 <https://wso2.org/jira/browse/APIMANAGER-925>] - New theme for API Store Improvements - [APIMANAGER-491 <https://wso2.org/jira/browse/APIMANAGER-491>] - Need an advanced search to locate a particular API, when there are loads of them, from store UI - [APIMANAGER-676 <https://wso2.org/jira/browse/APIMANAGER-676>] - Provide a UI to configure Tiers - [APIMANAGER-724 <https://wso2.org/jira/browse/APIMANAGER-724>] - Refresh token should not re-generate new tokens for tokens marked in-active - [APIMANAGER-744 <https://wso2.org/jira/browse/APIMANAGER-744>] - API search is case sensitive & support only exact searches - [APIMANAGER-747 <https://wso2.org/jira/browse/APIMANAGER-747>] - Include POST_TO_URI property by default to the API synapse configuration - [APIMANAGER-860 <https://wso2.org/jira/browse/APIMANAGER-860>] - Throttling Improvements - [APIMANAGER-907 <https://wso2.org/jira/browse/APIMANAGER-907>] - Deprecate the Login API and rename its url to /token Bug Fixes - [APIMANAGER-1 <https://wso2.org/jira/browse/APIMANAGER-1>] - [API docs] Attribute values are saved until page is refreshed - [APIMANAGER-7 <https://wso2.org/jira/browse/APIMANAGER-7>] - API MGR does not recover from lost connection to BAM server - [APIMANAGER-13 <https://wso2.org/jira/browse/APIMANAGER-13>] - Shouldn't we support -Dsetup for API Manager DB? - [APIMANAGER-104 <https://wso2.org/jira/browse/APIMANAGER-104>] - [API Store] Search is case sensitive. - [APIMANAGER-136 <https://wso2.org/jira/browse/APIMANAGER-136>] - [API Provider] When adding docs of type 'Other', though we specify a value it's not displayed anywhere. - [APIMANAGER-190 <https://wso2.org/jira/browse/APIMANAGER-190>] - Cannot change lifecycle states of APIs added through API-Manager - [APIMANAGER-349 <https://wso2.org/jira/browse/APIMANAGER-349>] - Provide users with option to edit API resources - [APIMANAGER-409 <https://wso2.org/jira/browse/APIMANAGER-409>] - [API Provider] When you change the Icon, you have to refresh the page to view the new Icon. - [APIMANAGER-710 <https://wso2.org/jira/browse/APIMANAGER-710>] - WSO2 AM generates un-necessary exceptions when Statistics are not enabled - [APIMANAGER-738 <https://wso2.org/jira/browse/APIMANAGER-738>] - Unable to set lifecycle state to PUBLISHED for APIs published through G-Reg - [APIMANAGER-750 <https://wso2.org/jira/browse/APIMANAGER-750>] - Cannot View APIs in API Publisher - [APIMANAGER-756 <https://wso2.org/jira/browse/APIMANAGER-756>] - API-Store tagCloud links not working for special charactors - [APIMANAGER-777 <https://wso2.org/jira/browse/APIMANAGER-777>] - Tier changes is not reflected as expected - [APIMANAGER-782 <https://wso2.org/jira/browse/APIMANAGER-782>] - NPE when editing inline doc content - [APIMANAGER-795 <https://wso2.org/jira/browse/APIMANAGER-795>] - Cannot invoke https endpoints with AM - [APIMANAGER-806 <https://wso2.org/jira/browse/APIMANAGER-806>] - When having multiple user stores cannot distinguish which role comes from which user-store, which becomes an issue when adding users. - [APIMANAGER-816 <https://wso2.org/jira/browse/APIMANAGER-816>] - <user1> and <domian.com>/<user1> are treated as two different users in AM-store for subscriptions - [APIMANAGER-821 <https://wso2.org/jira/browse/APIMANAGER-821>] - Revoked User Access tokens get produced in log in API call - [APIMANAGER-828 <https://wso2.org/jira/browse/APIMANAGER-828>] - Subscribers with same name but in different user-store can see/edit the subscriptions of the counterpart - [APIMANAGER-831 <https://wso2.org/jira/browse/APIMANAGER-831>] - Users with email address can't publish APIs - [APIMANAGER-838 <https://wso2.org/jira/browse/APIMANAGER-838>] - Samples broken in intermediate builds - [APIMANAGER-864 <https://wso2.org/jira/browse/APIMANAGER-864>] - Cannot invoke APIs when a WebContextRoot is specified in the carbon.xml - [APIMANAGER-865 <https://wso2.org/jira/browse/APIMANAGER-865>] - Error handling accented letter (à) - [APIMANAGER-867 <https://wso2.org/jira/browse/APIMANAGER-867>] - Need to properly handle character encoding of user entered content throughout the Jaggery apps - [APIMANAGER-874 <https://wso2.org/jira/browse/APIMANAGER-874>] - Issue on showing the status of API in 'overview' page once a life-cycle change happened - [APIMANAGER-875 <https://wso2.org/jira/browse/APIMANAGER-875>] - -Dsetup option fails after installing APIManager feature - [APIMANAGER-878 <https://wso2.org/jira/browse/APIMANAGER-878>] - ArrayIndexOutOfBoundsException when searching APIs with "version:" key - [APIMANAGER-879 <https://wso2.org/jira/browse/APIMANAGER-879>] - When searching APIs in publisher later versions are not shown - [APIMANAGER-880 <https://wso2.org/jira/browse/APIMANAGER-880>] - i18 key is shown as error message - [APIMANAGER-881 <https://wso2.org/jira/browse/APIMANAGER-881>] - [Publisher UI] When editing an API cannot change the visibility from public to Restricted - [APIMANAGER-882 <https://wso2.org/jira/browse/APIMANAGER-882>] - NPE when trying to update an API from publisher app - [APIMANAGER-883 <https://wso2.org/jira/browse/APIMANAGER-883>] - Bad Request when extra spaces are present in the Authorization header - [APIMANAGER-884 <https://wso2.org/jira/browse/APIMANAGER-884>] - Cannot subscribe to API's - [APIMANAGER-886 <https://wso2.org/jira/browse/APIMANAGER-886>] - SQL error thrown when invoking an API with an expired token - [APIMANAGER-887 <https://wso2.org/jira/browse/APIMANAGER-887>] - Recently Added APIs tab,doesn't show multiple versions of same API,when the related config is enabled - [APIMANAGER-888 <https://wso2.org/jira/browse/APIMANAGER-888>] - More APIs from provider tab,doesn't show multiple versions of same API,when the related config is enabled - [APIMANAGER-889 <https://wso2.org/jira/browse/APIMANAGER-889>] - Already Revoked Tokens lists when searching tokens - [APIMANAGER-891 <https://wso2.org/jira/browse/APIMANAGER-891>] - APISecurityException when load testing: Invalid use of SingleClientConnManager: connection still allocated. - [APIMANAGER-892 <https://wso2.org/jira/browse/APIMANAGER-892>] - Errors come in store when subscriber session becomes idle and refresh the page - [APIMANAGER-893 <https://wso2.org/jira/browse/APIMANAGER-893>] - API try it feature is broken - [APIMANAGER-894 <https://wso2.org/jira/browse/APIMANAGER-894>] - NPE thrown when changing the life cycle state from PUBLISHED to BLOCKED - [APIMANAGER-895 <https://wso2.org/jira/browse/APIMANAGER-895>] - Samples needed to be updated - [APIMANAGER-896 <https://wso2.org/jira/browse/APIMANAGER-896>] - Version number (1.2.0) is wrong in startup log - [APIMANAGER-897 <https://wso2.org/jira/browse/APIMANAGER-897>] - i18n key is shown for validation message in Sign up form in Store, Chrome only - [APIMANAGER-898 <https://wso2.org/jira/browse/APIMANAGER-898>] - Registry error when accessing /store - [APIMANAGER-899 <https://wso2.org/jira/browse/APIMANAGER-899>] - Application name in /store needs to be validated - [APIMANAGER-900 <https://wso2.org/jira/browse/APIMANAGER-900>] - API resource verbs are set to null in synapse level ,when edit an published API from publisher app - [APIMANAGER-901 <https://wso2.org/jira/browse/APIMANAGER-901>] - User login call for each API creation - [APIMANAGER-902 <https://wso2.org/jira/browse/APIMANAGER-902>] - Only one API with the version 1.0.0 is shown in store - [APIMANAGER-904 <https://wso2.org/jira/browse/APIMANAGER-904>] - Unexpected EOF in prolog Error, when sending a PUT - [APIMANAGER-906 <https://wso2.org/jira/browse/APIMANAGER-906>] - When accessing 'More APIs by Porvider' tab of Store app,in anonymous mode,backend errors thrown - [APIMANAGER-909 <https://wso2.org/jira/browse/APIMANAGER-909>] - Resource mappings does not update properly in component separated deployment - [APIMANAGER-910 <https://wso2.org/jira/browse/APIMANAGER-910>] - Token Partitioning feature cannot enable with Oracle because table creation fails due to ORA-00972: identifier is too long - [APIMANAGER-912 <https://wso2.org/jira/browse/APIMANAGER-912>] - Unable to open try it in a new tab - [APIMANAGER-917 <https://wso2.org/jira/browse/APIMANAGER-917>] - NPE in Gateway while doing loadtests - [APIMANAGER-918 <https://wso2.org/jira/browse/APIMANAGER-918>] - [LoadTests] API authentication fails periodically - [APIMANAGER-920 <https://wso2.org/jira/browse/APIMANAGER-920>] - "expires_in" value in /login call response is not timely accurate - [APIMANAGER-921 <https://wso2.org/jira/browse/APIMANAGER-921>] - Subscription UI is broken when the token is long - [APIMANAGER-922 <https://wso2.org/jira/browse/APIMANAGER-922>] - 404 - when accessing REST Client tool - [APIMANAGER-923 <https://wso2.org/jira/browse/APIMANAGER-923>] - ORA-00972: identifier is too long, error when token partitioning is enabled - [APIMANAGER-924 <https://wso2.org/jira/browse/APIMANAGER-924>] - API Store -When viewing documentation in anonymous mode,it throws errors in backend - [APIMANAGER-926 <https://wso2.org/jira/browse/APIMANAGER-926>] - Store tries to search for the API when you sign out while on the dashboard of a restricted API. - [APIMANAGER-927 <https://wso2.org/jira/browse/APIMANAGER-927>] - 'Subscriptions' for publisher page is empty and throws an ArrayIndexOutOfBound exception when token partitioning is enabled All resolved issues - WSO2 API Manager resolved issues<https://wso2.org/jira/secure/IssueNavigator.jspa?requestId=10888> 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. - API Publisher: - Publish APIs to external consumers and partners, as well as internal users; SOAP and REST services are supported - Manage API versions (several versions can be deployed in parallel) - Govern the API lifecycle (publish, deprecate, retire) - Attach documentation (files, external URLs) to APIs - Apply Security policies to APIs (authentication, authorization) - Attach SLAs - Provision and Manage API keys - Track consumers per API - Monitor API usage and performance, SLA compliance - Gather consumers requirements - API Consumers: - Find useful APIs by browsing or searching through the API Store: view top rated, top used and featured APIs - Explore API documentation and ask questions to publisher - Register applications and obtain API keys - Subscribe to API changes and receive news - Evaluate APIs, rate APIs, and share comments - Request features and improvements from publishers - Participate in online forums - OAuth2 support for API access Known Issues All the open issues pertaining to WSO2 API Manager are reported at the following location: - WSO2 API Manager open issues <https://wso2.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=10810> How You Can Contribute Mailing Lists Join our mailing list and correspond with the developers directly. - Developer List : dev@wso2.org | Subscribe<dev-requ...@wso2.org?subject=subscribe>| Mail Archive <http://wso2.org/mailarchive/dev/> - User List : u...@wso2.org | Subscribe<user-requ...@wso2.org?subject=subscribe>| Mail Archive <http://wso2.org/mailarchive/user/> 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. Support 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 visithttp://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 --*
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
