配置es的鉴权账号 Elasticsearch开启安全认证详细步骤

admin

启动集群：
& o/ v2 \( ~4 G' b, K" s: x
前提：设置好系统配置和JVM堆内存
4 E' u; f6 k0 q, q& [) }: O  K
3 F- c3 V9 x$ r  k8 ?: O创建elastic的数据和日志存放目录，如果是测试环境无所谓，如果是生成环境一定要单独设置数据和日志存放的路径，因为ES可能因为升级或其它原因把原有的数据清理或丢失等因素

! @/ L+ c  P2 ^$ o+ ^
1 h- w- w$ E8 D: A! C' T- I

+ [9 _: ?& j/ X配置文件属组权限，并启动
[root@it-elassearch elasticsearch]# chown -R es:es elastic-cluster1/
  C1 p! D$ A6 t! _7 G[root@it-elassearch-2 elasticsearch]# chown -R es:es elastic-cluster2/
4 b, A9 _6 j9 z4 ~
4 q* Y* V, \* n. H
6 R: n- Z5 k7 b+ y) N6 L
7 }. Z  S9 Z3 r: d如果添加鉴权配置请按照此处配置，不配置即可略过：
! w% J8 [7 W) o; g6 x
# X7 v, t6 i, X9 m; c
生成密匙：
' a8 r" O3 h: T! Y[es@it-elassearch elasticsearch-8.15.0]$ ./bin/elasticsearch-certutil ca
2 w- G6 W+ \1 uThis tool assists you in the generation of X.509 certificates and certificate
4 H+ s$ `0 [4 z( f9 P/ bsigning requests for use with SSL/TLS in the Elastic stack.

) ]/ c9 u2 Y7 M  X! |" F" A! a' P
The 'ca' mode generates a new 'certificate authority'
. `; B  x/ C" E2 PThis will create a new X.509 certificate and private key that can be used
to sign certificate when running in 'cert' mode.

% K$ _  v5 b. e6 H3 `. \( }9 E& E
Use the 'ca-dn' option if you wish to configure the 'distinguished name'
- A6 N3 a* \6 |/ Q* E9 s5 uof the certificate authority

3 l. S! ]  z: T5 @
By default the 'ca' mode produces a single PKCS#12 output file which holds:
& y5 B$ z; d: `3 |9 M    * The CA certificate
! d/ e1 c9 U, Z8 Z7 p    * The CA's private key
% X" f1 P5 \9 e) \

If you elect to generate PEM format certificates (the -pem option), then the output will
be a zip file containing individual files for the CA certificate and private key

Please enter the desired output file [elastic-stack-ca.p12]:         【这里忽略，直接回车进入下面输入密码：】
Enter password for elastic-stack-ca.p12 :    【输入密码】
- ^1 h- {; I, f: \7 h- d
0 p3 c1 Y" A# D' t) n4 t2 h# E+ C

4 e3 I1 d0 q' |7 ]2 }% l6 s# y) e[es@it-elassearch elasticsearch-8.15.0]$ ll
9 ]0 y2 z! K( |% @total 2268
......
-rw-------  1 es es    2672 Oct 28 17:05 elastic-stack-ca.p12
+ w# s5 t9 c/ ^0 e8 g) ^, ^0 S7 b......
' I; P1 \! p! O( ]7 \9 [

! U; M4 Q5 G5 W' x9 P! E' }- Q



[es@it-elassearch-2 elasticsearch-8.15.0]$ ./bin/elasticsearch-certutil ca
8 y0 d+ f1 \4 q, _8 s8 D# eThis tool assists you in the generation of X.509 certificates and certificate
9 @) I) m/ M) }) ]5 B  Hsigning requests for use with SSL/TLS in the Elastic stack.
1 o. x( g* m# |& U$ I: y1 s
+ f# f. [9 J* T; B1 w1 U
5 b: O# t/ d. j' @3 oThe 'ca' mode generates a new 'certificate authority'
This will create a new X.509 certificate and private key that can be used
6 W3 N, M, V8 L6 Z0 [to sign certificate when running in 'cert' mode.


# I8 }+ L( g5 L1 x" L/ pUse the 'ca-dn' option if you wish to configure the 'distinguished name'
! q5 s: [) s  }% j% M% m- Iof the certificate authority
, a. q4 I4 B& K7 A6 M$ Q

2 Z9 A& @4 n# zBy default the 'ca' mode produces a single PKCS#12 output file which holds:
    * The CA certificate
    * The CA's private key
: E9 K: s! W9 e! P' }/ [! I/ S) a

If you elect to generate PEM format certificates (the -pem option), then the output will
+ ]; [9 g; \" N8 M  ~be a zip file containing individual files for the CA certificate and private key
' [; ?5 g% p2 S) C3 d" u
$ [* W0 p% z1 Z
Please enter the desired output file [elastic-stack-ca.p12]:
% c- x4 h" V  a1 I6 h: q+ i4 HEnter password for elastic-stack-ca.p12 :
3 o6 z9 N. ~$ ~' H+ R' \: b

生成密钥：

/ W3 H2 O: p  i( ^
1 ^  S) f" ^3 G' V[es@it-elassearch elasticsearch-8.15.0]$ ./bin/elasticsearch-certutil cert --ca elastic-stack-ca.p12
This tool assists you in the generation of X.509 certificates and certificate
9 y* ]  k- Z8 L' N5 D: s' Z9 Zsigning requests for use with SSL/TLS in the Elastic stack.
3 W" s7 J+ @* r/ ^8 b
The 'cert' mode generates X.509 certificate and private keys.
    * By default, this generates a single certificate and key for use
       on a single instance.
8 U3 R# J: p' C* }% V    * The '-multiple' option will prompt you to enter details for multiple
       instances and will generate a certificate and key for each one
    * The '-in' option allows for the certificate generation to be automated by describing
       the details of each instance in a YAML file
; v' J  z2 {+ E2 h# R) y
& a. q1 K: j' c% k6 @* E3 ~% h- k    * An instance is any piece of the Elastic Stack that requires an SSL certificate.
: l# Y! q! }0 F6 m, X# Q      Depending on your configuration, Elasticsearch, Logstash, Kibana, and Beats
      may all require a certificate and private key.
) o: z. Y7 {; @2 C; J  t9 `# ]. _2 `    * The minimum required value for each instance is a name. This can simply be the
1 W2 Q( b7 D: X# ]. {- z      hostname, which will be used as the Common Name of the certificate. A full
      distinguished name may also be used.
    * A filename value may be required for each instance. This is necessary when the
7 W8 O4 t5 X9 K0 U      name would result in an invalid file or directory name. The name provided here
      is used as the directory name (within the zip) and the prefix for the key and
* E$ m4 S8 u; b      certificate files. The filename is required if you are prompted and the name
      is not displayed in the prompt.
    * IP addresses and DNS names are optional. Multiple values can be specified as a
& T0 b( v# Y* b6 v. c3 x( a9 D      comma separated string. If no IP addresses or DNS names are provided, you may
      disable hostname verification in your SSL configuration.


7 _/ `4 k# _/ c4 ^( F    * All certificates generated by this tool will be signed by a certificate authority (CA)
      unless the --self-signed command line option is specified.
      The tool can automatically generate a new CA for you, or you can provide your own with
1 B8 q& e( H& Y& J* Q      the --ca or --ca-cert command line options.
5 `7 L- Z  P9 V. g
, d1 A* k- s% L, G% z
) @' ?0 r# o3 Y+ T. E+ \  v5 {" |By default the 'cert' mode produces a single PKCS#12 output file which holds:
    * The instance certificate
5 H& X! Q1 i1 u' a6 _  _" e5 T    * The private key for the instance certificate
    * The CA certificate

; K$ _1 J; i+ ?6 G6 M2 DIf you specify any of the following options:
0 \0 E% n- x& J" h    * -pem (PEM formatted output)
    * -multiple (generate multiple certificates)
    * -in (generate certificates from an input file)
then the output will be be a zip file containing individual certificate/key files
* p8 ~3 Y7 ?' Y% m* n0 P
) }6 |& j$ B+ y7 l3 J8 l: m$ B/ lEnter password for CA (elastic-stack-ca.p12) :      【输入密码】
Please enter the desired output file [elastic-certificates.p12]:      【直接回车】
Enter password for elastic-certificates.p12 :     【再次输入密码】

1 {) _' u: j# ?4 p+ tCertificates written to /data/elasticsearch/elastic-cluster1/elasticsearch-8.15.0/elastic-certificates.p12

2 y% ?8 Q0 J: f4 V( tThis file should be properly secured as it contains the private key for
1 |$ r5 L: g+ _3 x  Z8 e) s: iyour instance.
5 Z4 @# k9 l2 w* ?* gThis file is a self contained file and can be copied and used 'as is'
" R/ |9 |& `0 `6 n& fFor each Elastic product that you wish to configure, you should copy
this '.p12' file to the relevant configuration directory
and then follow the SSL configuration instructions in the product guide.
, y0 l% @" W, I
For client applications, you may only need to copy the CA certificate and
7 W7 l9 ?0 P7 Z6 ~& S8 ]configure the client to trust this certificate.


+ U8 b: O+ R3 a6 I
[es@it-elassearch-2 elasticsearch-8.15.0]$ ./bin/elasticsearch-certutil cert --ca elastic-stack-ca.p12
This tool assists you in the generation of X.509 certificates and certificate
signing requests for use with SSL/TLS in the Elastic stack.

The 'cert' mode generates X.509 certificate and private keys.
  E* l3 k8 [4 o! j7 }    * By default, this generates a single certificate and key for use
( Y4 L" L$ r$ `! `& g  f       on a single instance.
: T, h( r4 o. P    * The '-multiple' option will prompt you to enter details for multiple
2 ~' y6 I* R5 P/ ]: [8 Y( e       instances and will generate a certificate and key for each one
  C  R; I) L0 A: l* M4 I    * The '-in' option allows for the certificate generation to be automated by describing
       the details of each instance in a YAML file
- \* A" Y; J1 s' f) h! }$ B
    * An instance is any piece of the Elastic Stack that requires an SSL certificate.
      Depending on your configuration, Elasticsearch, Logstash, Kibana, and Beats
      may all require a certificate and private key.
- L" Q. P2 W6 `9 H+ b# W    * The minimum required value for each instance is a name. This can simply be the
      hostname, which will be used as the Common Name of the certificate. A full
      distinguished name may also be used.
5 q1 }( L) E; D) o$ |    * A filename value may be required for each instance. This is necessary when the
      name would result in an invalid file or directory name. The name provided here
' O4 r: m1 R) ^- w8 S6 C& h      is used as the directory name (within the zip) and the prefix for the key and
      certificate files. The filename is required if you are prompted and the name
      is not displayed in the prompt.
    * IP addresses and DNS names are optional. Multiple values can be specified as a
      comma separated string. If no IP addresses or DNS names are provided, you may
4 z6 i. G* b7 ^) }) R      disable hostname verification in your SSL configuration.
. }6 W4 X1 [& o' T) m% d% [% g
) L5 L7 B8 M; k, t" B
8 N! r- w; B# ]- b. f, x. t    * All certificates generated by this tool will be signed by a certificate authority (CA)
9 W1 j6 R$ u, v' |& ~' G6 D      unless the --self-signed command line option is specified.
: L1 L; Y3 @' ]" F; y; _* ]4 J      The tool can automatically generate a new CA for you, or you can provide your own with
      the --ca or --ca-cert command line options.
$ I2 m: c6 r9 x& p! t+ t- e5 z

# S+ w! K& _9 o2 ]By default the 'cert' mode produces a single PKCS#12 output file which holds:
9 S5 r0 M; L+ T$ [# T    * The instance certificate
) r* z2 |& W/ w9 _0 R    * The private key for the instance certificate
    * The CA certificate

If you specify any of the following options:
    * -pem (PEM formatted output)
    * -multiple (generate multiple certificates)
, m1 Q5 P# }/ c2 l    * -in (generate certificates from an input file)
then the output will be be a zip file containing individual certificate/key files
& L2 V5 W6 u6 I  \1 @
Enter password for CA (elastic-stack-ca.p12) :   【输入密码】
! q: T! M# s; zPlease enter the desired output file [elastic-certificates.p12]:     【直接回车】
$ G5 c1 O3 v& T( w  ^, CEnter password for elastic-certificates.p12 :   【输入密码】

. `: g7 ~( K' C+ L; \9 XCertificates written to /data/elasticsearch/elastic-cluster2/elasticsearch-8.15.0/elastic-certificates.p12

This file should be properly secured as it contains the private key for
" n# ?! M7 o7 Fyour instance.
7 B- o1 J1 t; W$ w8 y' P9 C& l  HThis file is a self contained file and can be copied and used 'as is'
For each Elastic product that you wish to configure, you should copy
this '.p12' file to the relevant configuration directory
and then follow the SSL configuration instructions in the product guide.

For client applications, you may only need to copy the CA certificate and
6 s; ~9 L8 {, |configure the client to trust this certificate.

, }, L; A2 V- r: s& s. T
5 ]! V( p5 }) ^' K( `##将凭证迁移到指定的目录：
创建目录：
, d' w2 D' Z& h" H/ b4 d mkdir -p ./config/certificates/
) U/ i+ ^4 S  @% j" y8 P% v! @! G移动凭证到指定目录下：
mv elastic-certificates.p12 ./config/certificates/

赋于权限：


[es@it-elassearch elasticsearch-8.15.0]$ rsync -azvP -e 'ssh -p 22' config/certificates/elastic-certificates.p12 es@172.24.110.126:/data/elasticsearch/elastic-cluster2/elasticsearch-8.15.0/config/certificates/elastic-certificates.p12
The authenticity of host '[172.24.110.126]:22 ([172.24.110.126]:22)' can't be established.
ECDSA key fingerprint is SHA256:Tvzi0ICzurMYEPySzerkOmwk/o7XHxmABVKRigofHzg.
ECDSA key fingerprint is MD5:f0:92:26:fd:da:d3:e4:db:be:36:b1:fe:d6:2b:65:25.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '[172.24.110.126]:22' (ECDSA) to the list of known hosts.
* {3 A: ~9 Z" yes@172.24.110.126's password:
sending incremental file list
6 L4 |2 W9 L! i1 ?elastic-certificates.p12
& J- U( q9 O6 S8 c! j          3,596 100%    0.00kB/s    0:00:00 (xfr#1, to-chk=0/1)
. w: Q: c! X2 H
+ A0 i% g# n4 W: d% Y* l* o9 @$ e
8 }8 y+ V2 O' ?4 d/ i% B& lsent 3,631 bytes  received 35 bytes  564.00 bytes/sec
- g- S( B& j7 X! B) s( [1 wtotal size is 3,596  speedup is 0.98
* ^3 f2 X: a* g' o: P7 g
) \8 L! m( a/ [( f; ?修改配置文件（每台都需要添加）
) f  N8 `  L* q8 Q6 t5 p' ~5 S
/ C( Z6 N( }1 G& V6 w
: U0 H3 ^5 l% a- O  L$ a/ \http.cors.enabled: true
( T9 C& y4 w$ E; M1 shttp.cors.allow-origin: "*"
http.cors.allow-headers: Authorization,X-Requested-With,Content-Type,Content-Length

) ~+ {2 A* x# l7 w: A
) T5 k' x) `+ i( axpack.security.enabled: true
- Q- l! l; N3 nxpack.security.authc.accept_default_password: true
, z( g: |8 H& Nxpack.security.transport.ssl.enabled: true
' H, f2 W$ I  v5 v; d5 ixpack.security.transport.ssl.verification_mode: certificate
xpack.security.transport.ssl.keystore.path: ./config/certificates/elastic-certificates.p12
xpack.security.transport.ssl.truststore.path: ./config/certificates/elastic-certificates.p12

: S, ~$ a4 l+ d9 W4 A/ z) ~
在各个节点上添加密码：(每一台es都需要操作)

2 `- m% \/ U4 ?( t

) ~) A9 ~/ M7 A  e

/ p+ ]9 M5 V, W/ {* G& l加权一样需要切换到es账号：

在各个节点上添加密码：
) t/ c0 U* M# B" N( U
, u: T- V- Y, u% p[es@it-elassearch elasticsearch-8.15.0]$ ./bin/elasticsearch-keystore add xpack.security.transport.ssl.keystore.secure_password
[es@it-elassearch elasticsearch-8.15.0]$ ./bin/elasticsearch-keystore add xpack.security.transport.ssl.keystore.secure_password
Enter value for xpack.security.transport.ssl.keystore.secure_password:

: [7 \/ R0 g3 k1 ^& Q# I1 O% r
[es@it-elassearch-2 elasticsearch-8.15.0]$ ./bin/elasticsearch-keystore add xpack.security.transport.ssl.keystore.secure_password
Enter value for xpack.security.transport.ssl.keystore.secure_password:
输入密码：第一次输入密码
9 k2 s- n# `. x  S! \# Q
3 J1 H. a  K, B6 _6 N* B[es@it-elassearch elasticsearch-8.15.0]$ ./bin/elasticsearch-keystore add xpack.security.transport.ssl.truststore.secure_password
Enter value for xpack.security.transport.ssl.truststore.secure_password:

[es@it-elassearch-2 elasticsearch-8.15.0]$ ./bin/elasticsearch-keystore add xpack.security.transport.ssl.truststore.secure_password
Enter value for xpack.security.transport.ssl.truststore.secure_password:
4 Q% }: g6 C( o( M( E

输入密码： 第二次输入上面的密码：
4 C3 w. n9 R) P: f: r



* H. F% e% C4 q( J接下来和没有做鉴权的一样，逐个启动集群：
( S1 t4 u7 Z) o6 E  f' a* `6 o


$ T7 j/ J2 r( ~4 f0 D8 ~切换到其它用户，root用户不能启动ES：su es
- N8 A" Q6 ~. J0 e0 F  ~% e9 U9 J1 V
, X: V* K" Y) Z8 j, c7 m6 ?
+ Q( A" t4 X- }( C$ R0 b' `( e/ V
& [# g$ f- L4 Bbin/elasticsearch -d
[es@it-elassearch elasticsearch-8.15.0]$ bin/elasticsearch -d
& W5 _; j) i5 m4 Y. a& `

+ Y, q- l  V) ?6 y& u  A; j( y' r

2 K2 o$ q8 h: F: A+ W! h