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 GitHub Bot (JIRA)" <ji...@apache.org> on 2019/08/06 16:18:00 UTC

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

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

ASF GitHub Bot logged work on KNOX-1694:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 06/Aug/19 16:17
            Start Date: 06/Aug/19 16:17
    Worklog Time Spent: 10m 
      Work Description: moresandeep commented on pull request #126: KNOX-1694 - Prevent port mapped topologies from being exposed to gateway port
URL: https://github.com/apache/knox/pull/126
 
 
   (It is very **important** that you created an Apache Knox JIRA for this change and that the PR title/commit message includes the Apache Knox JIRA ID!)
   
   ## What changes were proposed in this pull request?
   Currently with topology port mapping feature, port mapped topologies are exposed on gateway port as well (default 8443) this is undesirable in a lot of cases. This feature locks the topologies that are mapped to specific port to only those ports and they are not exposed on the default gateway port. 
   
   ## How was this patch tested?
   There are new and old Unit tests added to test this feature. This patch was tested locally. Following cases were tested.
   
   1. Make sure topology port mapping feature works as expected.
   2. Make sure port mapped topologies are not exposed on gateway port.
   3. Make sure default topology feature works as expected.
   4. Make sure default topology can also be configured using port mapping configs.
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 289823)
            Time Spent: 10m
    Remaining Estimate: 0h

> 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: 10m
>  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)