You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@knox.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/08/06 18:29:00 UTC

[jira] [Commented] (KNOX-1694) Portmapping to lock down a topology only to a given port

    [ https://issues.apache.org/jira/browse/KNOX-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16901355#comment-16901355 ] 

ASF subversion and git services commented on KNOX-1694:
-------------------------------------------------------

Commit 55adc6a9cd59525f41159c5499ab214749887be9 in knox's branch refs/heads/master from Sandeep More
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=55adc6a ]

KNOX-1694 - Prevent port mapped topologies from being exposed to gateway port (#126)



> Portmapping to lock down a topology only to a given port
> --------------------------------------------------------
>
>                 Key: KNOX-1694
>                 URL: https://issues.apache.org/jira/browse/KNOX-1694
>             Project: Apache Knox
>          Issue Type: New Feature
>          Components: Server
>    Affects Versions: 1.3.0
>            Reporter: Sandeep More
>            Assignee: Sandeep More
>            Priority: Major
>             Fix For: 1.4.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently with port mapping enabled, a topology is exposed on the port-mapped port as well as on the configured gateway port (8443 - default), we need an ability to lock down the topology only yo port-mapped port so it cannot be accesses from other port/s.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)