[ https://issues.apache.org/jira/browse/ATLAS-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sarath Subramanian reopened ATLAS-2087: --------------------------------------- The following unit tests failed after the commit Failed tests: NegativeSSLAndKerberosTest.testUnsecuredClient:139 expected:<true> but was:<false> SSLAndKerberosTest.testService:185 » ClientHandler java.io.IOException: javax.... SSLTest.testService:147 » ClientHandler javax.net.ssl.SSLException: Unrecogniz... SecureEmbeddedServerTest>SecureEmbeddedServerTestBase.testMissingEntriesInCredentialProvider:143 No entries should generate an exception SecureEmbeddedServerTest>SecureEmbeddedServerTestBase.testNoConfiguredCredentialProvider:112 Should have thrown an exception SecureEmbeddedServerTest.testServerConfiguredUsingCredentialProvider:79 War deploy failed > Allow Atlas server to bind on a specific address > ------------------------------------------------ > > Key: ATLAS-2087 > URL: https://issues.apache.org/jira/browse/ATLAS-2087 > Project: Atlas > Issue Type: Improvement > Components: atlas-core > Affects Versions: 0.8-incubating > Reporter: Richard Ding > Assignee: Richard Ding > Fix For: 0.9-incubating > > Attachments: ATLAS-2087.2.patch, ATLAS-2087.patch > > > Atlas server always bind to address "0.0.0.0": > {code} > connector.setHost("0.0.0.0"); > {code} > But in many cases, user want to only run Atlas on a specified IP address > (e.g. private network). > The existing property "_atlas.server.bind.address_" should be used: > {code} > final String addr = conf.get("atlas.server.bind.address", "0.0.0.0"); > connector.setHost(addr); > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029)