Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Not A Bug
-
0.14.0
-
None
-
None
-
knox proxy and service discovery enabled
Description
Service discovery:
Verified knox proxy feature through the generated topology file from service discovery feature
Expectation:
=========
Generated topology file should have only the active atlas endpoint url , as HaProvider for atlas is not yet supported
when we access atlas through knox proxy, should'nt expose the atlas ip and port information.
Actual:
=====
Generated topology has both passive and active url for "ATLAS" service and passive url for "ATLAS-API" service.
Hence accessing atlas through knox proxy redirects me to the atlas active endpoint url, hence knox proxy fails.
Explained the failure case in scenario 1 below
Environment:
============
Atlas has 2 host
host1 - acive_host
host2 - passive_host
Scenario 1:
===========
Generated topology using service discovery feature
<service> <role>ATLAS</role> <url>http://{color:#FF0000}host2{color}:21000</url> <url>http://host1:21000</url> </service> <service> <role>ATLAS-API</role> <url>http://{color:#FF0000}host2{color}:21000</url> </service>
Here accessing the atlas through knox proxy redirects me to active atlas host1 url
accessing url : https://<gateway-host>:8443/gateway/ui/atlas
redirected url : http:/host1:21000/login.jsp
Scenario 2:
==============
when i manually modified the atlas endpoint to only active url in generated topology file then the knox proxy works fine
</gateway> <service> <role>ATLAS</role> <url>http://host1:21000</url> </service> <service> <role>ATLAS-API</role> <url>http://host1:21000</url> </service>
accessing url : https://gateway-host:8443/gateway/ui/atlas
redirected url: https://gateway-host:8443/gateway/ui/atlas/login.jsp