The WSO2 API Manager 1.5.0 Released!
The WSO2 API Manager team is pleased to announce the release of version 1.5.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
- Extract the downloaded zip
- Go to the bin directory in the extracted folder
- Run the wso2server.sh or wso2server.bat as appropriate
- Launch a web browser and navigate to https://localhost:9443/publisher to access the API provider webapp
- Navigate to https://localhost:9443/store to access the API store
- Use "admin", "admin" as the username and password to login as an admin
- If you need to start the OSGi console with the server use the property -DosgiConsole when starting the server. The INSTALL.txt file found on the installation directory will give you a comprehensive set of options and properties that can be passed into the startup script
New Features of WSO2 API Manager 1.5.0
This release of API Manager comes with a horde of new features and bug fixes.
New Features
- [APIMANAGER-1408] - Specifying expiration time for Application tokens
- [APIMANAGER-1415] - Support for different gateways for Production and Sandbox endpoints
- [APIMANAGER-1417] - Restricting exposed URLs of APIs for access via HTTPs only
- [APIMANAGER-1437] - Resource level throttling
- [APIMANAGER-1448] - Support for both super tenant and tenant stores in a single deployment
- [APIMANAGER-1449] - Load Balanced Data Publisher - publishing events to BAM/CEP
- [APIMANAGER-1465] - Support for Authorisation Code Grant type
- [APIMANAGER-1476] - Extension Point to associate sequences to inbound/outbound
- [APIMANAGER-1536] - Store API to retrieve all Documentation
Improvements
- [APIMANAGER-599] - Hide advanced options of API creation form to make it look simple & short
- [APIMANAGER-646] - Have all the mandatory fields of the API creation form at the top, tother
- [APIMANAGER-721] - Allow users to use custom headers for logic call response to api manager
- [APIMANAGER-742] - improve subscription management and display pages to clearly distinguish between app and app user tokens
- [APIMANAGER-931] - Improve fileUpload UI for API Documentations
- [APIMANAGER-1031] - Super Store population logic to be made more efficient
- [APIMANAGER-1040] - Update samples' script with the info
- [APIMANAGER-1311] - Restful API for programatically adding end users (subscribers) to API store
- [APIMANAGER-1347] - Published APIs shouldn't show details of proxied web services
- [APIMANAGER-1400] - Add a tool and an icon in the toolbar that allow to enter the LINK
- [APIMANAGER-1401] - Allow blocking only production access
- [APIMANAGER-1421] - Provide support for load balancing and failover on API Usage Tracking with BAM
- [APIMANAGER-1424] - Introduce secure-vault in APIManger configurations.
- [APIMANAGER-1425] - Provide support for adding more attributes for each tier level
- [APIMANAGER-1428] - APIM Performance Improvement
- [APIMANAGER-1429] - Creating an API for retrieving APIs subscribed under an Application
- [APIMANAGER-1461] - Encrypting access/refresh tokens
- [APIMANAGER-1502] - Add UI Improvements to My Subscriptions page in APIStore
- [APIMANAGER-1538] - Application Edit UI - UI Improvements 2
- [APIMANAGER-1539] - Application Edit UI - UI Improvements 3
- [APIMANAGER-1540] - Subscriptions UI - UI Improvements 1
- [APIMANAGER-1541] - Subscription UI - Context Sensitive Search
- [APIMANAGER-1544] - Replace Address Endpoint with HTTP Endpoint
- [APIMANAGER-1590] - There's considerable time delay(30sec) to start the wso2 carbon on the server start up
- [APIMANAGER-1603] - Same configuration and description for Thrift Key Validation server host name is mentioned twice in api-manager.xml
- [APIMANAGER-1608] - Cloud Identity (identity server) profile is loaded when logged in with a tenant to API Manager
- [APIMANAGER-1714] - Change Startup publisher configuration syntax
- [APIMANAGER-1718] - Integrate APIStore API listing pagination with registry pagination feature
- [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-1766] - Add functionality to update and delete comments added on an API
Bug Fixes
- [APIMANAGER-205] - Endpoint hardcoded in login API
- [APIMANAGER-785] - "Modified On" time does not get updated when document content is changed
- [APIMANAGER-823] - Store - Signup link changes localhost url call to IP/domain name based call
- [APIMANAGER-872] - [Store] User domain name is required when logging in to the store but the subscriber is not informed about the domain name.
- [APIMANAGER-885] - Problems while Installing/Running Full IS Features on top of API Manager
- [APIMANAGER-891] - APISecurityException when load testing: Invalid use of SingleClientConnManager: connection still allocated.
- [APIMANAGER-908] - API version is not mentioned in the API initialization log message
- [APIMANAGER-929] - Table missing in 1.3.0 PostgreSQL script
- [APIMANAGER-1120] - [MT mode] NPE thrown when clicking "Public API store" and go to "tenant's API store"
- [APIMANAGER-1146] - Long API Description is not handled correctly
- [APIMANAGER-1173] - If we give '/t/something' in the API context in tenant APIs then it will give 404 error when API is invoked
- [APIMANAGER-1194] - SSO is not working for tenant log in
- [APIMANAGER-1195] - Go to <User> Store is repeated when you click on the ? mark
- [APIMANAGER-1248] - [Chrome Version 26.0.1410.63] Documents are not downloaded, only shows a blank page
- [APIMANAGER-1257] - [Intermittent issue] State change from created to published, but it's not shown in Life-Cycle History
- [APIMANAGER-1260] - Email ID login does not support in multi tenancy mode
- [APIMANAGER-1262] - Search results in store show empty spaces in between
- [APIMANAGER-1271] - Com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was too long; max key length is 767 bytes
- [APIMANAGER-1305] - Issues when AD is secondary user store
- [APIMANAGER-1312] - Sandbox key can be generated although a sandbox URL does not exist
- [APIMANAGER-1316] - When a specific role is not given for an API which is restricted by roles, it will not display the tags, does not come in the search results and recently created APIs
- [APIMANAGER-1322] - Eventhough the invoking an API is successful INFO log is generated in KM - APIKeyMgtUtil Token null expired
- [APIMANAGER-1325] - UI layout changes once changed the theme
- [APIMANAGER-1330] - [Single sign out] Instead of signing out session time out message pops up
- [APIMANAGER-1331] - Tag search returns wrong number of results when two apis (public and restricted by tenants) share same tag
- [APIMANAGER-1333] - Wrong info shown if you mouse over Usage by Current Subscribers (v-2.0.0) graph (under users tab)
- [APIMANAGER-1336] - Billing Sample data is not accurate and java.lang.ClassCastException thrown when refreshing the page or when no data is available
- [APIMANAGER-1337] - [MT mode] Continuous error when deployment synchronizer is enabled
- [APIMANAGER-1340] - "WARN - LandingPageWebappDeployer Product landing page not found" at APIM-4.0 startup
- [APIMANAGER-1341] - Obsolete About doc in APIM-4.0.0
- [APIMANAGER-1342] - APIM-4.0 - "User guide" and "Docs" in login page are linked to APIM-1.3.0 doc
- [APIMANAGER-1343] - README of pizzashack should be updated
- [APIMANAGER-1344] - Error when deploying pizza-shack-web/target/pizzashack.war & pizza-shack-api/target/pizzashack-api-1.0.0.war in AS 5.0.0 or higher versions
- [APIMANAGER-1345] - Minor modification needed for README of YoutubeFeeds sample
- [APIMANAGER-1346] - README of TwitterSearch sampel should be updated
- [APIMANAGER-1348] - Errors not handled correctly in REST API for Generate Application Keys
- [APIMANAGER-1349] - [IE8] APIs are not shown after adding api - have to navigate to publisher/browse (but api added successfully)
- [APIMANAGER-1350] - http://docs.wso2.org/wiki/display/AM140/Quick+Start is outdated
- [APIMANAGER-1351] - GET is useless in swagger based tryit
- [APIMANAGER-1352] - Unclassified Authentication Failure is returned when value of referer is not in allowed domain list
- [APIMANAGER-1354] - Multiple tokens (and consumer key/secrets) can be created for a single Application
- [APIMANAGER-1355] - When no Locale file exists for the browser language, default Locale file is not picked.
- [APIMANAGER-1357] - org.wso2.carbon.apimgt.api fails to build as of r174865
- [APIMANAGER-1358] - Restful Store API allows users to examine other user credentials
- [APIMANAGER-1360] - Thrift aspects in the context of port offset need documentation
- [APIMANAGER-1362] - Multi-tenant semantics for API-M needs to be documentd
- [APIMANAGER-1363] - Exceptions in APIStore- My Subscriptions page,when an API visibility change from public to restricted
- [APIMANAGER-1364] - Add role validation to 'restricted' visibility entry of Add API page in API Publisher app
- [APIMANAGER-1365] - When a user creates an API with a URL which has got query parameters, it saves without the URL and does not prompt any error message until the lifecycle change
- [APIMANAGER-1366] - AM's port offset is not shown in the clustering initialization logs in ELB
- [APIMANAGER-1369] - Cannot create APIs with users logged in with email-addresses to APIPublisher
- [APIMANAGER-1372] - [Sample - Pizza Shack] - Sample information needs to be updated.
- [APIMANAGER-1374] - Token being passed published to BAM instead of the consumer key
- [APIMANAGER-1375] - Error when Using AM with LDAP
- [APIMANAGER-1377] - RESTClient: in-secure way of passing username
- [APIMANAGER-1381] - The start ratings does not appear in the module "recently added".
- [APIMANAGER-1382] - UI glitches : typos and resizing issues
- [APIMANAGER-1387] - Issues with billing sample
- [APIMANAGER-1389] - API manager services cannot be invoked via AF. 404 returned and a registry asked for username and password in store
- [APIMANAGER-1390] - API Manager /store API login does not work for tenant users
- [APIMANAGER-1393] - API context validation issue at API creation
- [APIMANAGER-1394] - 401 Error: Unauthorized exception thrown when trying login to API Manager by changing the backend Server URL (to a different one than specified in carbon.xml) prior to login
- [APIMANAGER-1395] - Add claim management feature to API manager
- [APIMANAGER-1398] - False information in APIM docs
- [APIMANAGER-1403] - [Intermittent]Token API response does not contain any data.
- [APIMANAGER-1404] - When logged in with a tenant to API manager carbon console, got the following exceptions with a NullPointer
- [APIMANAGER-1405] - Invocation Target Exception when listing APIs in API-M Mgt console, in tenant mode
- [APIMANAGER-1406] - Problem returning 204 No Content through WSO2 API Manager
- [APIMANAGER-1411] - Secured Proxy Service not working when deployed on API Manager
- [APIMANAGER-1412] - Cannot invoke an API with thrift enabled
- [APIMANAGER-1413] - Store Sign UP page has "null" as a field value
- [APIMANAGER-1414] - Error in API Key Validation when thrift enabled
- [APIMANAGER-1416] - No APIs shown in APIStore anonymous mode
- [APIMANAGER-1418] - API Gateway worker nodes does not reflect port offset in a worker manager separated cluster
- [APIMANAGER-1430] - Implement resource level throttling for API manager
- [APIMANAGER-1431] - Regenerate button is not showing
- [APIMANAGER-1432] - After regenerating the application token storeUI shows older token
- [APIMANAGER-1433] - Showing error logs when accessing APIStore
- [APIMANAGER-1438] - Swagger UI page in APIStore broken
- [APIMANAGER-1439] - Cannot change tiers for a create API
- [APIMANAGER-1440] - Array Index out of bounds exception when trying to update API
- [APIMANAGER-1442] - When regenerate newer tokens..DB is not getting updated
- [APIMANAGER-1447] - Error when adding multiple resources to an API
- [APIMANAGER-1451] - Unable to decode a SAML request
- [APIMANAGER-1456] - Store inaccessible after creating a tenant - Embedded API Manager
- [APIMANAGER-1457] - Only one subscriber shown in Subscribers page
- [APIMANAGER-1458] - API can be invoked even the status is changed to Blocked or Retired
- [APIMANAGER-1459] - WARN - ItemGroupSelector Error while i18ning ItemGroupSelector - When listing APIs
- [APIMANAGER-1462] - NPE When shutting down API-M
- [APIMANAGER-1463] - SSO doesn't work with API-M
- [APIMANAGER-1466] - authorize endpoint does not work for "implicit" grant type
- [APIMANAGER-1467] - Encrypting access/refresh tokens
- [APIMANAGER-1469] - Restricted By Tenant option is available in visibility drop down when editing and API
- [APIMANAGER-1470] - Creating an application directs to the login page, not the app detail page and user has to re login.
- [APIMANAGER-1471] - Roles restricted APIs for tenants are not visible
- [APIMANAGER-1472] - Clicking on tags do not list down the related APIs
- [APIMANAGER-1473] - Sandbox key also getting blcoked even when we blocked the 'Production Only' subscriptions
- [APIMANAGER-1474] - When a user is not logged in, store does not show the tags of the APIs visible in public store
- [APIMANAGER-1475] - Users who SignUp via store of a Tenant, not get created under that Tenant
- [APIMANAGER-1477] - Adding URL documentation makes API edit inactive
- [APIMANAGER-1478] - Tags created for an API which is restricted only for a particular role are appeared for other roles as well.
- [APIMANAGER-1480] - API Remove Ratings functionality does not work as expected
- [APIMANAGER-1481] - More APIs from a particular publisher are not listed down when you click on an API.
- [APIMANAGER-1482] - Create an API or Publish an API throwing exception sometimes
- [APIMANAGER-1483] - Production URL and sandbox should be marked as mandotory by a *
- [APIMANAGER-1484] - [WINDOWS] Re-generate Key in tenant mode throwing exception
- [APIMANAGER-1485] - Cannot search for APIs of tenant users in anonymous mode of tenant store view
- [APIMANAGER-1486] - Store allows non-tenant users to login when there are multiple Tenants
- [APIMANAGER-1487] - Access Token in Store can be edited since its displayed in a text box field
- [APIMANAGER-1488] - Token validity value enetered in to Edit box is not saved
- [APIMANAGER-1489] - Subscriptions block unblock functionality does not work as expected
- [APIMANAGER-1491] - Exception occurred while publishing the created API and publishing the versions
- [APIMANAGER-1493] - API becomes unresponsive after adding document through URL
- [APIMANAGER-1494] - Response body is removed when invoking APIs
- [APIMANAGER-1495] - Error in sample â Access YouTube Feeds Using an APIâ
- [APIMANAGER-1498] - Append additional CORS headers comes from the endpoint without overriding
- [APIMANAGER-1499] - Cannot regenerate the sandbox keys
- [APIMANAGER-1501] - Include API Manager logo in mgt console in tenancy mode.
- [APIMANAGER-1504] - Intermitteng Cache initializing issue when invoking APIs and cannot invoke any other APIs
- [APIMANAGER-1506] - Super tenant can login to store even after tenants were created
- [APIMANAGER-1507] - Edit and Save a doc pops-up an empty window
- [APIMANAGER-1508] - username is not initialized in apistore /api/listing/ajax/list.jag
- [APIMANAGER-1509] - Customized default Token period not reflected in the UI
- [APIMANAGER-1510] - Docs and About links in mgt console direct to documentation version 1.4.1
- [APIMANAGER-1511] - Re-generate link get hide after re-generating the Access Token
- [APIMANAGER-1512] - Cannot startup APIM/ESB server properly
- [APIMANAGER-1513] - Unnecessary test text in Throttling info section
- [APIMANAGER-1514] - Navigate to certain pages in Management Console result in dead page
- [APIMANAGER-1515] - Added documents for API are not displaying in API Store
- [APIMANAGER-1516] - Application directs the user to blank page after copying the API
- [APIMANAGER-1518] - When there are more APIs, clicking on next pages go to a dead page when the user is not logged in tenant mode
- [APIMANAGER-1519] - Store Header goes missing when the logged in tenant user clicks on next page in APIs listing page
- [APIMANAGER-1520] - In Tenant mode, Invoking API using Production token when only Sanbox url configured, it doesn't give a proper Error Message.
- [APIMANAGER-1522] - When the user is not logged in tenant mode, it will show the non tenant users created public APIs in Recently created API sections when you click on the next
- [APIMANAGER-1523] - Users getting logout from store ,if we create a new application while subscribing to API
- [APIMANAGER-1524] - Error occurred while removing the added document
- [APIMANAGER-1527] - Adding new Throttling tiers take time to update defined in cache.xml in tenancy mode
- [APIMANAGER-1530] - [UI] A "null" text in "Throttling info" section in store
- [APIMANAGER-1531] - API Docs - Edit content, shows and empty message
- [APIMANAGER-1532] - [REST client] Get requests with sub resources in the context url doesnt work
- [APIMANAGER-1533] - [REST Client] Cannot add http headers to the POST PUT DELETE requests
- [APIMANAGER-1534] - Store header go missing when the user selects a different application with subscriptions from the drop down
- [APIMANAGER-1535] - Error when executing AM table creation script for MySQL
- [APIMANAGER-1546] - Once an API is updated in publisher, it will save and direct to the versions page
- [APIMANAGER-1547] - When a user updates API icon, it is updated after 15 minutes
- [APIMANAGER-1548] - Mutual tags given for an API are not updated when a user edits it
- [APIMANAGER-1549] - Updated Tier Permission values are not saved. Always reset once you refresh
- [APIMANAGER-1551] - Swagger editor integration in Docs does not work as expected
- [APIMANAGER-1552] - [Intermittent] Registry username and password is asked in store
- [APIMANAGER-1553] - Error when running YouTube sample
- [APIMANAGER-1566] - Tier Availability levels are not getting updated. Updates only during a server restart
- [APIMANAGER-1567] - API Update does not work correctly in tenant mode
- [APIMANAGER-1568] - Once throttle:Attributes are added in to a defined tier, API cannot be invoked
- [APIMANAGER-1570] - Exception throws when invoking token API to generate user tokens from SAML2 assertions
- [APIMANAGER-1571] - Unable to regenerate the access token once after the SAML2Grant configs changes in the identity.xml,
- [APIMANAGER-1572] - Token validity period changes when the user set the token validity period as never expired (-1)
- [APIMANAGER-1574] - Cannot startup APIM with embedded apacheds ldap configuration enabled
- [APIMANAGER-1576] - "Store" can be accessed when started with publisher profile
- [APIMANAGER-1577] - "publisher" can be accessed when started with "store" profile
- [APIMANAGER-1578] - Revoke Token feature is broken
- [APIMANAGER-1582] - Delete an application which has subscribed to an API causing the subscription page to break
- [APIMANAGER-1584] - API Manager tables are not getting created in oracle database
- [APIMANAGER-1585] - [Statistics][BAM] Even when BAM is configured but if there is no data in Statistics db; still the Publisher's statistics page shows "Sample; Configure BAM to see yours" page
- [APIMANAGER-1586] - Publisher and Store jaggery apps are very slow to respond in any request in standalone API M instance
- [APIMANAGER-1588] - Exception throws when AM configured with BAM (MySql) access the statistics page in the publisher
- [APIMANAGER-1592] - SAML SSO redirection does not work
- [APIMANAGER-1594] - Invoking via swagger does not work correctly via firefox
- [APIMANAGER-1596] - Login to Store with a tenant user works partially
- [APIMANAGER-1597] - [Documentation issue] Given curl command in the Exchanging SAML2 bearer tokens with OAuth2 is wrong.
- [APIMANAGER-1599] - [Caching issue]Tenant user with subscribe permissions could not create a Application in Store, until for sometime, after the user is created
- [APIMANAGER-1600] - Given error message is wrong when try to login to the publiser with wrong credentials
- [APIMANAGER-1601] - After the initial logged in to a tenant and checked out for statistics it shows a graph which is keep on initializing.
- [APIMANAGER-1604] - When APIM configured with 2 BAM instances, its not properly load balanced among nodes when the primary node is down.
- [APIMANAGER-1607] - When port offset set Re-generate key not working in store
- [APIMANAGER-1610] - Cannot see APIs through Management Console while logged in with a tenant admin
- [APIMANAGER-1612] - Changing of configuration of API did not get reflected in the Publisher UI
- [APIMANAGER-1614] - When sets 1000 concurrent requests to the APIM following exception throws in the BE
- [APIMANAGER-1615] - Following exception throws when invoking tenant api through bulk set of jmeter requests, once after the server start up
- [APIMANAGER-1617] - [Intermittent][UI] Following exception throws when removing an API.
- [APIMANAGER-1624] - tenant-mgt.xml is not available in the AM 1.5.0 RC1 pack
- [APIMANAGER-1625] - Exception throws once accessing the publisher statistics when APIM retrieve stats from BAM which is connected to oracle DB
- [APIMANAGER-1626] - Application Access Token is recieved as the User Token via OAuth grant types
- [APIMANAGER-1627] - API Updated time in Store is always the API created time
- [APIMANAGER-1628] - Format button in Swagger documentation does not work as expected
- [APIMANAGER-1631] - Subscriptions page break once the user login to a different tenant store via "Public API Store" link
- [APIMANAGER-1633] - Overall subscription percentage per API count is wrong (102%). It should be 100%
- [APIMANAGER-1635] - When API Manager instance is fronted by ELB with Proxy Ports are configured; when API Manager is starting up; those proxy ports are not appened in the urls logged; rather append the API Manager instances http and https ports
- [APIMANAGER-1636] - [Documentation] Some configuration details are missing in WSO2BAM configuration
- [APIMANAGER-1638] - When running with burst of 100 requests(/jaxrs_basic sample as end point) some requests (randomly) are getting authentication failures and request are getting failed.
- [APIMANAGER-1641] - Unable to login to the API publisher for a tenant user which is created on a secondary user store (MySql)
- [APIMANAGER-1642] - Unable to edit API for tenant an admin user when there's secondary user store attached to the tenant domain (There should be a tenant user on the secondary user store as similar to tenant admin username)
- [APIMANAGER-1643] - Tenant Admin created APIs are not visible in the store, recently added APIs section
- [APIMANAGER-1644] - Once you delete an app from the store, My subscription page goes blank. Notification is not provided.
- [APIMANAGER-1645] - [OpenLDAP] When trying to log in to publisher or store it fails because it tries to create empty 'subscriber' role
- [APIMANAGER-1647] - Error when creating AM_DB for Oracle
- [APIMANAGER-1648] - AxisFault: Error initializing API handler : When changing life cycle from created to public
- [APIMANAGER-1651] - [Intermittent] Cannot add APIs in tenant mode - due to not having permission to update reg resource
- [APIMANAGER-1652] - Error when loading tenant store when there are no APIs published
- [APIMANAGER-1654] - Access Token Partitioning is not working
- [APIMANAGER-1655] - When JWTCache is enabled and GatewayKeyCache is disabled caching does not happen
- [APIMANAGER-1656] - User can invoke using both previous and new access tokens even after refreshing the access token
- [APIMANAGER-1657] - Publish to External API Store; Flow; Display in External Store saved option lost
- [APIMANAGER-1658] - Some stats data getting reduced once let one BAM server down and let the other BAM server to load balance the stats data.
- [APIMANAGER-1659] - Display in External Store comes only with Edit API
- [APIMANAGER-1661] - When create a API as restricted by roles for a role which is created on a secondary user store, its visible to all users in that user store
- [APIMANAGER-1663] - Tier Permissions functionality does not work for Secondary user store users
- [APIMANAGER-1664] - Subscription block unblock functionality does not work for secondary user store users
- [APIMANAGER-1665] - API M single gateway node cannot be started due to not building the fault sequence
- [APIMANAGER-1666] - Secondary user store user (admin domain) created API's in the publisher are not visible in the store.
- [APIMANAGER-1667] - Statistics are not visible for a secondary user store (admin domain) user though the same API details are shown when accessing the All statistics page.
- [APIMANAGER-1668] - Instead of saying no data found, it says "Refer our wiki to configure BAM correctly" in API Usage By User in publisher statistics.
- [APIMANAGER-1669] - Secondary user store user doesn't allow to logged in without mentioning the user store domain.
- [APIMANAGER-1671] - Application list not showing when primary db set as Oracle 10g
- [APIMANAGER-1673] - ERROR {org.wso2.carbon.core.persistence.AbstractPersistenceManager} - Unable to handle service initialization error when started with API-M profile gateway-worker
- [APIMANAGER-1675] - Theme-ing broken in API-M in tenant mode
- [APIMANAGER-1676] - When you change the life cycle status - it always show as Changed the API status from '' to Created
- [APIMANAGER-1678] - When a API is invoked and when the request is dispatched to Gateway Worker; it goes through the local transport
- [APIMANAGER-1679] - API publishing to gateway is shown as failed in the ui; with exceptions in the backend but get's published to gateway in the distributed setup
- [APIMANAGER-1680] - Some of the public APIs and tags go missing from the store in anonymous tenant mode
- [APIMANAGER-1681] - "Allowed Domains" are not updated in the database
- [APIMANAGER-1683] - Allowed Domains feature not working properly
- [APIMANAGER-1684] - Error while creating and publishing APIs in distributed set up tenant mode
- [APIMANAGER-1685] - IDN_OPENID_USER_RPS table is not created via postgresql script
- [APIMANAGER-1686] - Issue in creating an API
- [APIMANAGER-1689] - When the store is restarted, APIs go missing in anonymous mode in distributed set up tenant mode. User has to login and logout
- [APIMANAGER-1690] - Other tenants's API tags can be viewed in annonymous mode and when you click on the tags those APIs canbe viewed in a different tenant
- [APIMANAGER-1691] - API comment feature in store is broken in PSQL
- [APIMANAGER-1692] - Some of the features in Store API does not work as expected.
- [APIMANAGER-1694] - Rich test editor is not working when trying to edit tier.xml in registry
- [APIMANAGER-1696] - "Time created" value of a OAUTH2 token get updated to the time when the token is revoked
- [APIMANAGER-1697] - "APPLICATION TOKEN" is provided as the "APPLICATION_USER TOKEN for the same username password, even after APPLICATION_TOKEN is expired.
- [APIMANAGER-1698] - APPLICATION_USER Token is later converted to an APPLICATION token
- [APIMANAGER-1699] - Sandbox keys are supported in Environment type="production" mode
- [APIMANAGER-1700] - HTTP 200 OK response is returned when a SANDBOX token is used on a PRODUCTION gateway
- [APIMANAGER-1701] - Registry pagination doesn't work with APIM -Listing APIs
- [APIMANAGER-1702] - Cannot create sandbox tokens; Oracle DB
- [APIMANAGER-1705] - Store: Subscriptions page shows an incomplete page with an exception: for a tenant: for a user with only subscriber permissions
- [APIMANAGER-1706] - uri-template feature is broken
- [APIMANAGER-1707] - [Intermittent] API does not get created. just the creating button stays as loading.
- [APIMANAGER-1708] - APIUsageByUser graph does not getting loaded with Oracle
- [APIMANAGER-1709] - First GET request for an API fails in the distributed setup
- [APIMANAGER-1710] - Remove Raw Link from swagger UI
- [APIMANAGER-1713] - Inconsistent result from search api in publisher and store webapp apimanager 1.4.0
- [APIMANAGER-1716] - Issue in changing the API status in to published
- [APIMANAGER-1717] - Tier permissions changes are not saved when the DB is used as PSQL
- [APIMANAGER-1719] - Faulty graph does not get loaded
- [APIMANAGER-1720] - API Manager Store requests redirecting IP address from the localhost.
- [APIMANAGER-1721] - Token mgt SQL error with Oracle in Publisher node
- [APIMANAGER-1722] - Error when getting an Identity Persistence Store instance
- [APIMANAGER-1723] - When custom sequences are invoked in API level, message body gets dropped for POST PUT methods
- [APIMANAGER-1724] - APIs per page growing with number of the page
- [APIMANAGER-1725] - APIs are not visible on the store. Only shown in the recently added and when you click on the tags
- [APIMANAGER-1726] - Cannot install APIM keymanager features to IS
- [APIMANAGER-1727] - When RequiredRespHeaderClaimUris is enabled token api does not work for tenant users since the attributes are not set properly
- [APIMANAGER-1728] - Cannot login to IS as a tenant after installing KeyManagement features in IS
- [APIMANAGER-1732] - Error - Illegal access attempt to cache
- [APIMANAGER-1733] - Store APIs are not sorted
- [APIMANAGER-1734] - External APIStores related UI,still showing in add API page,even after it seperated from create API process
- [APIMANAGER-1735] - Length of searched APIs doesn't show correctly in APIStore
- [APIMANAGER-1737] - API invocations fails for tenants when JWT token enabled in a distributed setup
- [APIMANAGER-1743] - APIs cannot be invoked. APISecurityException occured
- [APIMANAGER-1744] - Unable to generate keys after editing the token validity time.
- [APIMANAGER-1745] - When I provide the default OUT Sequence or a custom out seq in adding a Mediation Extension response will come in binary format
- [APIMANAGER-1746] - APIs does not getting listed in the store, when <DisplayAllAPIs> is set to true in api-manager.xml
- [APIMANAGER-1747] - Indicate as "invalid" when validate https endpoint URI's
- [APIMANAGER-1749] - Subscriptions are not visible for other users
- [APIMANAGER-1751] - Added Documentations are not visible for a copied API when the user is not logged in
- [APIMANAGER-1752] - Cannot login to API Manager when userstore is configured with openldap
- [APIMANAGER-1754] - When a new tier is added in to tiers.xml and try to invoke an API, Error processing the throttling policy error comes for every API
- [APIMANAGER-1755] - Defined additional tier attributes are not visible for a newly added tier.
- [APIMANAGER-1756] - Unable to access the created API after enabling the token encryption
- [APIMANAGER-1757] - Publisher pagination should not be limited to 10 API's as shown in the attached image
- [APIMANAGER-1759] - Can subscribe to a published api through subscribe-add.jag store api, with any throttling policy. So it will not honour the throttling policy specified by the publisher
- [APIMANAGER-1760] - When an API is copied for an existing version, it doesnt give a validation message. It stays on the same screen
- [APIMANAGER-1761] - Time stamp value is printed for sometime in the Date of User Registration once you click on it. But after sometimes it will show the correct value.Time stamp value is printed for sometime in the Date of User Registration
- [APIMANAGER-1762] - Store webapp; Listing APIs, browsing through the pages of API list is very slow.
- [APIMANAGER-1764] - Following exception throws in key manager while some of the API invocations fail when sending burst of 1000 requests, (Consider the endpoint is secured with UT)
- [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-1768] - When an API is created with a Publisher user; The browser redirect to the all APIs page; but not the created API page; So the user again need to search through APIs to find the last created one
- [APIMANAGER-1770] - [Documentation] Incorrect details in, Saving Access Tokens in Separate Tables document
- [APIMANAGER-1771] - Self Sign up - when a user try signing up with an already existing username; the backend gives an exception but no error in the UI
- [APIMANAGER-1772] - Generated user token saved in the wrong table even after the Access Token Partitioning has configured.
- [APIMANAGER-1773] - Access Token regeneration failed with changing the token validity period
- [APIMANAGER-1774] - After configured, Login with email funcationality, its allowing the user to login to management console using email but not allowing to login in to the publiser or store.
- [APIMANAGER-1775] - Add api fails with a registry error - during a volume test
- [APIMANAGER-1776] - Changes to Life Cycle are not visible in External stores
- [APIMANAGER-1777] - Created API is visible to every user, though its visibility Restricted by roles
- [APIMANAGER-1778] - java.lang.NullPointerException is printed when regenrating keys for apps when the thrift client is enabled
- [APIMANAGER-1780] - Error while publishing the API after changing and reverting back the API templates.
- [APIMANAGER-1781] - Publiser search doesn't work when the user search with an wild card word
- [APIMANAGER-1782] - Unable to logged in to the store, got an read time out exception
- [APIMANAGER-1783] - Keys cannot be regenerated.
- [APIMANAGER-1784] - Eventhough the server is restarted, an old app name will be printed in JWT caching
- [APIMANAGER-1785] - When JWT token and claims are enabled in api-manager.xml, apis cannot be invoked
- [APIMANAGER-1786] - Cannnot login to Store for tenants
- [APIMANAGER-1789] - [Documentation] Update the SSO UI screens according to the new IS released version
All 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 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 customization.
- 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 customers
- 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 application
- 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:
How You Can Contribute
Mailing Lists
Join our mailing list and correspond with the developers directly.
- Developer List : dev@wso2.org | Subscribe | Mail Archive
- User List : user@wso2.org | 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. You can use the Carbon JIRA 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 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 --