[
https://issues.apache.org/jira/browse/SYNAPSE-953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiranya Jayathilaka resolved SYNAPSE-953.
-----------------------------------------
Resolution: Fixed
Fix Version/s: (was: 1.1.1)
NIGHTLY
Patch applied with some modifications:
1. Changed the attribute name from "transports" to "transport" (it only
supports a single protocol name)
2. Used the getIncomingTransportName() method to get the transport name instead
of getTransport().getName(). (This is consistent with the Resource class)
3. Added separate serialization test cases
4. Added a new test case in APIDispatcherTest
Thanks Ruwan for the contribution.
> Introducing transport level (HTTPs etc.) access restriction to Rest APIs
> ------------------------------------------------------------------------
>
> Key: SYNAPSE-953
> URL: https://issues.apache.org/jira/browse/SYNAPSE-953
> Project: Synapse
> Issue Type: New Feature
> Components: Core
> Affects Versions: 1.1
> Reporter: Ruwan
> Assignee: Hiranya Jayathilaka
> Labels: features, patch
> Fix For: NIGHTLY
>
> Attachments: rest_api_transport_access_restriction.patch,
> rest_api_transport_access_restriction_v2.patch
>
>
> There is no way to enforce transport level access restrictions to APIs, like
> on proxy services.
> This can be addressed by adding a property called "transports" to the API
> configuration XML, based on which, access to said API can be granted or
> deflected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
