elastic/elasticsearch

Do not allow setting xpack.security.user when running as a node

Open

#29,751 opened on Feb 10, 2017

View on GitHub
 (4 comments) (0 reactions) (0 assignees)Java (25,882 forks)batch import
:Security/Security>enhancementTeam:Securityhelp wanted

Repository metrics

Stars
 (76,700 stars)
PR merge metrics
 (Avg merge 2d) (1,000 merged PRs in 30d)

Description

Original comment by @jaymode:

I think we've thought about this but never did anything about it because we used shield.user in the test framework. In master we no longer use shield.user for node clients and we should probably fail on startup if someone sets shield.user and isn't running as a transport client.

Contributor guide

Research direction
Investigate the use of xpack.security.user setting in node startup and enforce a check to fail if set when not running as transport client.
Tech stack
java
Domain
security
Issue type
Security
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaElasticsearch
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40