*WSO2 API Manager 2.0.0-M1 Released!* WSO2 API Manager team is pleased to announce WSO2 API Manager 2.0.0 -M1 release. Download distribution here <https://svn.wso2.org/repos/wso2/scratch/2016/apim-2.0.0/wso2am-2.0.0-SNAPSHOT-M1.zip>. This release contains following bug fixes, improvements, new features and tasks. Bug Fixes
- [APIMANAGER-1337 <https://wso2.org/jira/browse/APIMANAGER-1337>] - [MT mode] Continuous error when deployment synchronizer is enabled - [APIMANAGER-1674 <https://wso2.org/jira/browse/APIMANAGER-1674>] - Re-generate Key from UI should remove from KeyManager Cached Key for consistency - [APIMANAGER-1784 <https://wso2.org/jira/browse/APIMANAGER-1784>] - Eventhough the server is restarted, an old app name will be printed in JWT caching - [APIMANAGER-2375 <https://wso2.org/jira/browse/APIMANAGER-2375>] - Resource not found exception when tenant getting loaded on gateway node - [APIMANAGER-2408 <https://wso2.org/jira/browse/APIMANAGER-2408>] - when registry path is there as wsdl url test option will not work. - [APIMANAGER-2420 <https://wso2.org/jira/browse/APIMANAGER-2420>] - Subscription related usability issue - [APIMANAGER-2496 <https://wso2.org/jira/browse/APIMANAGER-2496>] - Http 500 error page after creating a new topic in the forum, in tenant mode - [APIMANAGER-2624 <https://wso2.org/jira/browse/APIMANAGER-2624>] - Issue with forum display on firefox [Intermittent] - [APIMANAGER-2636 <https://wso2.org/jira/browse/APIMANAGER-2636>] - Inconsistency in API Manager consent page - Deny action - [APIMANAGER-2749 <https://wso2.org/jira/browse/APIMANAGER-2749>] - Logging in with email from profile attribute - email is not supported - [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-2859 <https://wso2.org/jira/browse/APIMANAGER-2859>] - Foceful shutdown throws exceptions - [APIMANAGER-2869 <https://wso2.org/jira/browse/APIMANAGER-2869>] - Issue with Store loading when email based SSO log in is enabled - [APIMANAGER-2974 <https://wso2.org/jira/browse/APIMANAGER-2974>] - WorkFlows: Multiple Tasks are created for the same production application registration and sanbox application registration - [APIMANAGER-2994 <https://wso2.org/jira/browse/APIMANAGER-2994>] - Workflows: The user is granted access eventhough the wrong task is approved - [APIMANAGER-3156 <https://wso2.org/jira/browse/APIMANAGER-3156>] - UI issues in Publisher - [APIMANAGER-3210 <https://wso2.org/jira/browse/APIMANAGER-3210>] - Issue in the Access Token 'Copy to clipboard' function - [APIMANAGER-3365 <https://wso2.org/jira/browse/APIMANAGER-3365>] - OAuth Cache is not invalidated when an application is deleted - [APIMANAGER-3372 <https://wso2.org/jira/browse/APIMANAGER-3372>] - I/O operations in a synchronized block - [APIMANAGER-3463 <https://wso2.org/jira/browse/APIMANAGER-3463>] - API Publisher page loading time highly increase with no of APIs incresed - [APIMANAGER-3549 <https://wso2.org/jira/browse/APIMANAGER-3549>] - When update the original application tier it allows one request addition to the throttling limit in APIM 1.9.0 SNAPSHOT - [APIMANAGER-3659 <https://wso2.org/jira/browse/APIMANAGER-3659>] - Throttling not replicated correctly on Gateway cluster for tenant APIs - [APIMANAGER-3756 <https://wso2.org/jira/browse/APIMANAGER-3756>] - Inline JavaScript is failing when the last line is a comment - [APIMANAGER-4082 <https://wso2.org/jira/browse/APIMANAGER-4082>] - enableJWTassertion creates extra 'assertion' header in API requests - [APIMANAGER-4118 <https://wso2.org/jira/browse/APIMANAGER-4118>] - Renaming an application using the store API seems to mess up subscriptions page in store - [APIMANAGER-4126 <https://wso2.org/jira/browse/APIMANAGER-4126>] - Reverse Proxy with Tenants on Carbon - [APIMANAGER-4292 <https://wso2.org/jira/browse/APIMANAGER-4292>] - Issues occur when resources have & or & - [APIMANAGER-4297 <https://wso2.org/jira/browse/APIMANAGER-4297>] - Remove key manager issue due to connection issue to thrift server - [APIMANAGER-4306 <https://wso2.org/jira/browse/APIMANAGER-4306>] - Admin-dashboard allowed role name for default admin role is hard coded - [APIMANAGER-4317 <https://wso2.org/jira/browse/APIMANAGER-4317>] - Error while generating keys for a new application [Intermittent] - [APIMANAGER-4341 <https://wso2.org/jira/browse/APIMANAGER-4341>] - [Tenant mode]Number of concurrent requests exceeds the application throttling limit in large scale when a hard throttling limit has enabled and the hard throttling limit > application throttling limit - [APIMANAGER-4448 <https://wso2.org/jira/browse/APIMANAGER-4448>] - Editing an API with an inline script does not show the implementation method as inline - [APIMANAGER-4466 <https://wso2.org/jira/browse/APIMANAGER-4466>] - Exception with Tenant null while dowloading WSDL on store - [APIMANAGER-4467 <https://wso2.org/jira/browse/APIMANAGER-4467>] - In ApplicationDeletionWorkflow; (ApplicationWorkflowDTO) workflowDTO.getApplication().getSubscribedAPIs() always returns an empty set. - [APIMANAGER-4471 <https://wso2.org/jira/browse/APIMANAGER-4471>] - API Visibility Restrictions are not working when direct URLs of APIs are used - [APIMANAGER-4473 <https://wso2.org/jira/browse/APIMANAGER-4473>] - Modifications to Default API executor - [APIMANAGER-4479 <https://wso2.org/jira/browse/APIMANAGER-4479>] - When API lifecycle is changed back to created stage, API store still list that API as a result for a doc content search. - [APIMANAGER-4480 <https://wso2.org/jira/browse/APIMANAGER-4480>] - In APIM Store 1.9.1 get all subscription API broke backward compatibility - [APIMANAGER-4481 <https://wso2.org/jira/browse/APIMANAGER-4481>] - API store lists documents of deprecated APIs as a search result of doc content search - [APIMANAGER-4482 <https://wso2.org/jira/browse/APIMANAGER-4482>] - REST API Store functionality fails if the user is not logged in at least once by Store webapp - [APIMANAGER-4487 <https://wso2.org/jira/browse/APIMANAGER-4487>] - Failed to change the life cycle status :Invoking lifecycle action "Publish" failed OK - [APIMANAGER-4494 <https://wso2.org/jira/browse/APIMANAGER-4494>] - Use 'X-Forwarded-For' header instead of 'REMOTE_ADDR' to identify client IP - [APIMANAGER-4496 <https://wso2.org/jira/browse/APIMANAGER-4496>] - Can't view API overview in anonymous mode - [APIMANAGER-4497 <https://wso2.org/jira/browse/APIMANAGER-4497>] - Some columns are missing in Oracle_rac db scripts. - [APIMANAGER-4498 <https://wso2.org/jira/browse/APIMANAGER-4498>] - When updating tier permission system saves invalid role names after giving a validation message. - [APIMANAGER-4499 <https://wso2.org/jira/browse/APIMANAGER-4499>] - Exception thrown when clicked on API after migration of APIM from 1.9.1 to 1.10.0 - [APIMANAGER-4503 <https://wso2.org/jira/browse/APIMANAGER-4503>] - When user saves a permission tier without a role and refresh the page, tiers permission breaks and gives a 'NullPointerException' - [APIMANAGER-4504 <https://wso2.org/jira/browse/APIMANAGER-4504>] - "Invalid signature" error while verifying the JWT token generated by Api manager. - [APIMANAGER-4513 <https://wso2.org/jira/browse/APIMANAGER-4513>] - Incorrect error message is returned when there is no matching URL mapping. - [APIMANAGER-4514 <https://wso2.org/jira/browse/APIMANAGER-4514>] - Incorrect URL template is picked for the requested API resource path. - [APIMANAGER-4517 <https://wso2.org/jira/browse/APIMANAGER-4517>] - Admin-Dashboard - Proxy Port not updated for Throttling Tiers - [APIMANAGER-4519 <https://wso2.org/jira/browse/APIMANAGER-4519>] - Admin-Dashboard - modernizr.custom.js is missing - [APIMANAGER-4522 <https://wso2.org/jira/browse/APIMANAGER-4522>] - Deployed a patch WSO2-AM-1.7.0-SP01, which when we start the API Manager it returns errors - [APIMANAGER-4523 <https://wso2.org/jira/browse/APIMANAGER-4523>] - HTTPSender Unable to sendViaPost to url[ https://65.39.201.7:9443/services/RemoteAuthorizationManagerService] - [APIMANAGER-4524 <https://wso2.org/jira/browse/APIMANAGER-4524>] - API Manager SSO logout issue for multiple users - [APIMANAGER-4532 <https://wso2.org/jira/browse/APIMANAGER-4532>] - Store/Publisher of tenant fails to load if an API in the database gets corrupted - [APIMANAGER-4547 <https://wso2.org/jira/browse/APIMANAGER-4547>] - Intermittent : issue when login to store in distributed setup with SSO enabled - [APIMANAGER-4558 <https://wso2.org/jira/browse/APIMANAGER-4558>] - &tenant=carbon.super missing - [APIMANAGER-4567 <https://wso2.org/jira/browse/APIMANAGER-4567>] - Custom status message is not retained in the response when using the passthrough transport - [APIMANAGER-4572 <https://wso2.org/jira/browse/APIMANAGER-4572>] - [Distributed setup] Retired and Blocked APIs are shown in store - [APIMANAGER-4574 <https://wso2.org/jira/browse/APIMANAGER-4574>] - [Distributed setup] Published APIs are not shown in store - [APIMANAGER-4578 <https://wso2.org/jira/browse/APIMANAGER-4578>] - Cannot generate keys for Default application with Oracle11g due to an issue in oracle.sql script - [APIMANAGER-4594 <https://wso2.org/jira/browse/APIMANAGER-4594>] - [Intermittent] [ERROR] Unable to load throttling policy using key: gov:/apimgt/applicationdata/tiers.xml Improvements - [APIMANAGER-3965 <https://wso2.org/jira/browse/APIMANAGER-3965>] - Per API CORS Configuration - [APIMANAGER-4383 <https://wso2.org/jira/browse/APIMANAGER-4383>] - Change the error message into a meaningful one that get after exceeding the hard throttling limit in APIM logs. - [APIMANAGER-4413 <https://wso2.org/jira/browse/APIMANAGER-4413>] - Include different error codes when throttling out in different throttling levels - [APIMANAGER-4475 <https://wso2.org/jira/browse/APIMANAGER-4475>] - API authentication error response should bear the message type provided the Accept header of the request - [APIMANAGER-4476 <https://wso2.org/jira/browse/APIMANAGER-4476>] - Need an automation test for testing the Default Endpoint feature - [APIMANAGER-4488 <https://wso2.org/jira/browse/APIMANAGER-4488>] - Performance issue when updating an application - [APIMANAGER-4492 <https://wso2.org/jira/browse/APIMANAGER-4492>] - More log information about APISecurityException - [APIMANAGER-4527 <https://wso2.org/jira/browse/APIMANAGER-4527>] - Upgrade Swagger Editor and UI - [APIMANAGER-4531 <https://wso2.org/jira/browse/APIMANAGER-4531>] - Prevent the Signature Verification Error log for tenants - [APIMANAGER-4555 <https://wso2.org/jira/browse/APIMANAGER-4555>] - WSO2 Product APIM builds unstable Tasks - [APIMANAGER-4470 <https://wso2.org/jira/browse/APIMANAGER-4470>] - Cleanup and fix API.rxt - [APIMANAGER-4486 <https://wso2.org/jira/browse/APIMANAGER-4486>] - Remove the UI for enabling analytics - [APIMANAGER-4489 <https://wso2.org/jira/browse/APIMANAGER-4489>] - Restructure the apimgt.core feature - [APIMANAGER-4490 <https://wso2.org/jira/browse/APIMANAGER-4490>] - Remove duplicate api-manager.xml config file from build - [APIMANAGER-4491 <https://wso2.org/jira/browse/APIMANAGER-4491>] - product-apim does not use the key-manager feature You can find the complete lists of resolved issues and know issues below. Resolved Issues: https://wso2.org/jira/issues/?filter=13004 Known Issues: https://wso2.org/jira/issues/?filter=13005 Thanks, APIM team
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
