maxmustermann/kibana
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
kibana/x-pack/plugins/security
History
Aleh Zasypkin 411a3fbbbc
Use refresh token for any access token error with 401 status code and re-authentication user for any refresh token error with 400 status code. (#33777) 
* Use refresh token for any access token error with 401 status code and re-initiate SAML handshake for any refresh token error with 400 status code.

* Switch from `expect.js` to `@kbn/expect`.

* Review#1: repurpose redundant tests to test token failures with 500 code.
2019-03-27 15:09:33 +01:00
..
common [eslint] require final newline (#32265) 2019-02-28 18:01:29 -08:00
public Migration to Babel7 and @babel/preset-typescript (#33093) 2019-03-26 20:44:03 +00:00
server Use refresh token for any access token error with 401 status code and re-authentication user for any refresh token error with 400 status code. (#33777) 2019-03-27 15:09:33 +01:00
index.js Security - authorization mode request cache (#33248) 2019-03-15 14:55:01 -07:00
README.md

README.md

Kibana Security Plugin

  1. Install the Security plugin on Kibana bin/kibana plugin --install kibana/security/latest
  2. Modify kibana.yml and add xpack.security.encryptionKey: "something_at_least_32_characters"
  3. Make sure that the following config options are also set: elasticsearch.username, elasticsearch.password, server.ssl.certificate, and server.ssl.key (see Configuring Kibana to Work with Shield)

Once done, open up the following url (assuming standard kibana config): https://localhost:5601.