[
https://issues.apache.org/jira/browse/KNOX-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandeep More updated KNOX-1694:
-------------------------------
Description: 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 to port-mapped port
so it cannot be accesses from other port/s. (was: 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.)
> 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 to port-mapped port so it cannot be
> accesses from other port/s.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
