Skip to content

Don't force binding to 127.0.0.1 when using AnyoneSecurityProvider#101

Merged
asfgit merged 1 commit intoapache:masterfrom
neykov:fix/skip-security
May 13, 2016
Merged

Don't force binding to 127.0.0.1 when using AnyoneSecurityProvider#101
asfgit merged 1 commit intoapache:masterfrom
neykov:fix/skip-security

Conversation

@neykov
Copy link
Member

@neykov neykov commented Apr 5, 2016

Keeps backwards compatibility - using AnyoneSecurityProvider wouldn't force brooklyn server to bind to loopback only, but then changed to being treated same as noSecurityProvider. Revert to initial behaviour.

/cc @johnmccabe

@johnmccabe
Copy link
Contributor

@neykov I'm seeing it bind to all interfaces as expected now, but we still see the loopback logged to the console. I can't recall seeing it log that its bound to all interfaces in the past but it might be nice to show that for correctness.

@neykov
Copy link
Member Author

neykov commented Apr 5, 2016

@johnmccabe It's meant as a simple copy&paste aid (or click for terminals that support it). So better to use a real address.

Keeps backwards compatibility - using AnyoneSecurityProvider wouldn't force brooklyn server to bind to loopback only, but then changed to being treated same as noSecurityProvider. Revert to initial behaviour.
@neykov neykov force-pushed the fix/skip-security branch from fcbc941 to 64bb70d Compare April 8, 2016 07:03
@asfgit asfgit merged commit 64bb70d into apache:master May 13, 2016
asfgit pushed a commit that referenced this pull request May 13, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants