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

fleet-server username/password authentication must be removed in 8.0 #978

Closed
jlind23 opened this issue Dec 8, 2021 · 4 comments · Fixed by elastic/observability-docs#1423
Assignees
Labels
Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team v8.0.0

Comments

@jlind23
Copy link
Contributor

jlind23 commented Dec 8, 2021

Describe the enhancement:
Write access to Elasticsearch using username/password must be totally removed.

Describe a specific use case for the enhancement or feature:

@elasticmachine
Copy link
Collaborator

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

@jlind23 jlind23 transferred this issue from elastic/beats Dec 8, 2021
@jlind23 jlind23 added Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team v7.16.0 v8.0.0 and removed v7.16.0 labels Dec 8, 2021
@ruflin
Copy link
Member

ruflin commented Dec 8, 2021

It needs to be made sure also all the related code in Elastic Agent is removed too.

@michel-laterman
Copy link
Contributor

username/password has been removed from the fleet-server and elastic-agent in 8.1 and backported to 8.0.
The docs pr for this is: elastic/observability-docs#1423

@jlind23 jlind23 changed the title fleet-server username/password authentication must be removed in 8.0 #1845 fleet-server username/password authentication must be removed in 8.0 Jan 6, 2022
@dikshachauhan-qasource
Copy link

Hi @jlind23

We have validated this ticket on 8.0 rc1 BC1 build self managed environment and found it working fine there.

Steps included:

  • Set up a self managed env on 8.0 rc1 bc1 build.
  • Access Kibana and install Fleet server agent under Default fleet server policy.
  • Wait agent to be available on Fleet and running as Healthy.
  • Now access location: C:\Program Files\Elastic\Agent and open Fleet.yml file
  • Scroll down to outputs section.

Observation:

  • No username and password key were available in Fleet.yml under output section.
  • Service token value was available.
output:
      elasticsearch:
        protocol: https
        hosts:
        - 10.0.7.38:9200
        service_token: AAEAAWVsYXN0aWMvZmxlZXQtc2VydmVyL3Rva2VuLTE2NDE5MDAzNTk1NjA6SXZ4d29zSnZTY0M5a3kxbVFoalItQQ

Screenshot:
image

Build details:

BUILD 48917
COMMIT 51f4ded427abb6fd96c7d65e179fb367d450448c
Artifact link: https://staging.elastic.co/8.0.0-rc1-da1f5893/summary-8.0.0-rc1.html

Thanks
QAS

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team v8.0.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants