*WSO2 API Manager 1.5.0, RC2 Released !*

The second RC build of WSO2 API Manager 1.5.0, can be downloaded from [1].
Please find a summary of all changes/bug fixes, listed below.

Bug Fixes

   - [APIMANAGER-1479 <https://wso2.org/jira/browse/APIMANAGER-1479>] -
   Couldn't change the Thumbnail Image
   - [APIMANAGER-1480 <https://wso2.org/jira/browse/APIMANAGER-1480>] - API
   Remove Ratings functionality does not work as expected
   - [APIMANAGER-1495 <https://wso2.org/jira/browse/APIMANAGER-1495>] -
   Error in sample “ Access YouTube Feeds Using an API”
   - [APIMANAGER-1505 <https://wso2.org/jira/browse/APIMANAGER-1505>] -
   Intermittent Cache initializing error - Embedded API Manager
   - [APIMANAGER-1510 <https://wso2.org/jira/browse/APIMANAGER-1510>] -
   Docs and About links in mgt console direct to documentation version 1.4.1
   - [APIMANAGER-1517 <https://wso2.org/jira/browse/APIMANAGER-1517>] -
   Resource Level Throttling does not work as expected
   - [APIMANAGER-1545 <https://wso2.org/jira/browse/APIMANAGER-1545>] -
   Application level Throttling Tier always set as Unlimited
   - [APIMANAGER-1553 <https://wso2.org/jira/browse/APIMANAGER-1553>] -
   Error when running YouTube sample
   - [APIMANAGER-1556 <https://wso2.org/jira/browse/APIMANAGER-1556>] -
   [Distributed]API Invocation fails when using WSClient
   - [APIMANAGER-1558 <https://wso2.org/jira/browse/APIMANAGER-1558>] -
   APIMGT MSSQL script not running on MSSQL 2012
   - [APIMANAGER-1564 <https://wso2.org/jira/browse/APIMANAGER-1564>] -
   Store header goes missing when a user unsubscribe by removing the
   subscription
   - [APIMANAGER-1565 <https://wso2.org/jira/browse/APIMANAGER-1565>] -
   Users can subscribe to APIs eventhough there are no subscription level tiers
   - [APIMANAGER-1566 <https://wso2.org/jira/browse/APIMANAGER-1566>] -
   Tier Availability levels are not getting updated. Updates only during a
   server restart
   - [APIMANAGER-1567 <https://wso2.org/jira/browse/APIMANAGER-1567>] - API
   Update does not work correctly in tenant mode
   - [APIMANAGER-1568 <https://wso2.org/jira/browse/APIMANAGER-1568>] -
   Once throttle:Attributes are added in to a defined tier, API cannot be
   invoked
   - [APIMANAGER-1570 <https://wso2.org/jira/browse/APIMANAGER-1570>] -
   Exception throws when invoking token API to generate user tokens from SAML2
   assertions
   - [APIMANAGER-1575 <https://wso2.org/jira/browse/APIMANAGER-1575>] -
   Calling token API and revoke api via HTTPS is broken
   - [APIMANAGER-1578 <https://wso2.org/jira/browse/APIMANAGER-1578>] -
   Revoke Token feature is broken
   - [APIMANAGER-1580 <https://wso2.org/jira/browse/APIMANAGER-1580>] -
   When request url not contains a forward slash not getting any response
   - [APIMANAGER-1584 <https://wso2.org/jira/browse/APIMANAGER-1584>] - API
   Manager tables are not getting created in oracle database
   - [APIMANAGER-1587 <https://wso2.org/jira/browse/APIMANAGER-1587>] -
   When EnableJWTCache=true with claims, APIs cannot be invoked
   - [APIMANAGER-1592 <https://wso2.org/jira/browse/APIMANAGER-1592>] -
   SAML SSO redirection does not work
   - [APIMANAGER-1594 <https://wso2.org/jira/browse/APIMANAGER-1594>] -
   Invoking via swagger does not work correctly via firefox
   - [APIMANAGER-1595 <https://wso2.org/jira/browse/APIMANAGER-1595>] -
   Store APIs go missing when clicking on tags in tenant mode
   - [APIMANAGER-1602 <https://wso2.org/jira/browse/APIMANAGER-1602>] -
   Recently created APIs go missing from store
   - [APIMANAGER-1618 <https://wso2.org/jira/browse/APIMANAGER-1618>] -
   Once an API is blocked and try to publish Update button goes un responsive
   (disable)
   - [APIMANAGER-1620 <https://wso2.org/jira/browse/APIMANAGER-1620>] -
   Already subscribed user can subscribe to a deprecated API via a different
   application
   - [APIMANAGER-1621 <https://wso2.org/jira/browse/APIMANAGER-1621>] -
   Life cycle history does not show the latest activities in publisher
   - [APIMANAGER-1622 <https://wso2.org/jira/browse/APIMANAGER-1622>] - API
   provider is not shown when a user clicks in More APIs from section on an
   API in a different state in store
   - [APIMANAGER-1627 <https://wso2.org/jira/browse/APIMANAGER-1627>] - API
   Updated time in Store is always the API created time
   - [APIMANAGER-1629 <https://wso2.org/jira/browse/APIMANAGER-1629>] -
   User roles cannot be created in tenant mode when the user store is pointed
   to LDAP
   - [APIMANAGER-1639 <https://wso2.org/jira/browse/APIMANAGER-1639>] -
   [Intermittent] Issues in caching in permission in store side and login


Improvements

   - [APIMANAGER-1537 <https://wso2.org/jira/browse/APIMANAGER-1537>] -
   Application Edit UI - UI Improvements 1
   - [APIMANAGER-1538 <https://wso2.org/jira/browse/APIMANAGER-1538>] -
   Application Edit UI - UI Improvements 2
   - [APIMANAGER-1539 <https://wso2.org/jira/browse/APIMANAGER-1539>] -
   Application Edit UI - UI Improvements 3
   - [APIMANAGER-1540 <https://wso2.org/jira/browse/APIMANAGER-1540>] -
   Subscriptions UI - UI Improvements 1
   - [APIMANAGER-1541 <https://wso2.org/jira/browse/APIMANAGER-1541>] -
   Subscription UI - Context Sensitive Search


Tasks

   - [APIMANAGER-1579 <https://wso2.org/jira/browse/APIMANAGER-1579>] -
   Tenant-mgt.xml not packed in APIM




Your feedback is most welcome !!! Please report all the Jiras at [3] and
specify the version as 1.5.0
RC2<https://wso2.org/jira/browse/APIMANAGER/fixforversion/11042>
.


[1]
http://builder3.us1.wso2.org/builds/chunk-02/N_12-09-13/AM/wso2am-1.5.0_RC2.zip
[2] AM Roadmap :
https://wso2.org/jira/browse/APIMANAGER#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel
[3] https://wso2.org/jira/browse/APIMANAGER



Thanks and Regards,

Ruwan Yatawara

Software Engineer,
WSO2 Inc.
lean . enterprise . middleware

email : [email protected]
mobile : +94 77 9110413
blog : http://ruwansrants.blogspot.com/
www: :http://wso2.com
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to