[
https://issues.apache.org/jira/browse/KNOX-1694?focusedWorklogId=289920&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-289920
]
ASF GitHub Bot logged work on KNOX-1694:
----------------------------------------
Author: ASF GitHub Bot
Created on: 06/Aug/19 18:28
Start Date: 06/Aug/19 18:28
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
----------------------------------------------------------------
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:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 289920)
Time Spent: 20m (was: 10m)
> 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)
