[
https://issues.apache.org/jira/browse/SYNAPSE-953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13723263#comment-13723263
]
Hiranya Jayathilaka commented on SYNAPSE-953:
---------------------------------------------
If I understood correct, this feature is identical to the protocol attribute
already supported by resources, but at the API level instead of at resource
level. Am I correct?
In that case can you please refactor your code (especially the canProcess
method) to be similar to what the Resource.canProcess() method does? Basically,
try to use the same protocol constants from RESTConstants (PROTOCOL_HTTP_ONLY,
PROTOCOL_HTTPS_ONLY etc.)
> 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: 1.1.1
>
> Attachments: rest_api_transport_access_restriction.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]
