Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configure anonymous token policy for connect #230

Merged
merged 1 commit into from
Mar 19, 2020

Commits on Mar 19, 2020

  1. Configure anonymous token policy for connect

    When running Consul Connect, cross-dc calls require that the anonymous
    token has read permissions on all services. This change updates the
    server-acl-init command to give the anonymous token those permissions if
    connect is enabled.
    
    Since we already set those permissions in the case of dns being enabled,
    the change was to also set those permissions in the case of connect
    being enabled. To detect connect being enabled, we used the presence of
    the -create-inject-auth-method flag since that's set when connect is
    enabled.
    
    The policy was renamed from dns-policy to anonymous-token-policy since
    it applies for more than just dns now. In existing installations, a new
    policy with that name will be created and attached to the anonymous
    token that will duplicate the old dns-policy but will have no
    detrimental effects.
    lkysow committed Mar 19, 2020
    Configuration menu
    Copy the full SHA
    7fd044f View commit details
    Browse the repository at this point in the history