Merge branch 'master' into develop

Author: Dzuming

details/fls-engine.md

@@ -1,6 +1,6 @@
 # FLS engine
 
-Applicable in the context of the [`fields` rule](elasticsearch#fields) 
+Applicable in the context of the [`fields` rule](../elasticsearch.md#fields) 
 
 FLS engine specifies how ROR handles field-level security internally. Previously FLS was based entirely on [Lucene](https://en.wikipedia.org/wiki/Apache_Lucene) - that's why ROR needed to be installed on all nodes to make the `fields` rule work properly.
 Now the `fields` rule is more flexible and part of FLS responsibilities is handled solely by ES. Increasing ES usage and reducing Lucene exploitation in FLS implementation makes the rule more efficient.

details/kibana-7.8.x-and-older.md

@@ -665,7 +665,7 @@ readonlyrest:
       signature_key: "my_shared_secret_kibana1_(min 256 chars)" # <- use environmental variables for better security!
 ```
 
-You may also use any custom claim from the OIDC `userinfo` token in ACL rules by using `{{jwt:assertion.<path_to_your_claim>}}` syntax. See the [Dynamic variables from JWT claims section](elasticsearch##usage-examples) for more information. ( **TIP** : Do not forget the `assertion` prefix in front of you jsonpath. )
+You may also use any custom claim from the OIDC `userinfo` token in ACL rules by using `{{jwt:assertion.<path_to_your_claim>}}` syntax. See the [Dynamic variables from JWT claims section](../elasticsearch.md#usage-examples) for more information. ( **TIP** : Do not forget the `assertion` prefix in front of you jsonpath. )
 
 ### Kibana side
 

eck.md

@@ -104,7 +104,7 @@ metadata:
   name: config-readonlyrest.yml
 ```
 
-Notice that if you use ROR Enterprise, you can take advantage of the [Cluster-wide Settings](kibana#cluster-wide-settings-vs-readonlyrest.yml) functionality and reload configuration on all your nodes without restarting K8s' PODs. 
+Notice that if you use ROR Enterprise, you can take advantage of the [Cluster-wide Settings](kibana.md#cluster-wide-settings-vs-readonlyrest.yml) functionality and reload configuration on all your nodes without restarting K8s' PODs. 
 
 #### Kibana node with ReadonlyREST plugin
 

elasticsearch.md

@@ -8,7 +8,7 @@ The Elasticsearch plugin known as `ReadonlyREST Free` is released under the GPLv
 
 Unlike the Elasticsearch plugin, the Kibana plugins are commercial only. But rely on the Elasticsearch plugin in order to work.
 
-For a description of the Kibana plugins, skip to the [dedicated documentation page](kibana) instead.
+For a description of the Kibana plugins, skip to the [dedicated documentation page](kibana.md) instead.
 
 ### ReadonlyREST Free plugin for Elasticsearch
 
@@ -437,7 +437,7 @@ _An Example of the Access Control List \(ACL\) made of 2 blocks._
 
 The YAML snippet above, like all of this plugin's settings should be saved inside the `readonlyrest.yml` file. Create this file **on the same path where `elasticsearch.yml` is found**.
 
-**TIP**: If you are a subscriber of the [PRO](https://readonlyrest.com/pro) or [Enterprise](https://readonlyrest.com/enterprise) Kibana plugin, you can edit and refresh the settings through a GUI. For more on this, see the [documentation for the ReadonlyREST plugin for Kibana](kibana).
+**TIP**: If you are a subscriber of the [PRO](https://readonlyrest.com/pro) or [Enterprise](https://readonlyrest.com/enterprise) Kibana plugin, you can edit and refresh the settings through a GUI. For more on this, see the [documentation for the ReadonlyREST plugin for Kibana](kibana.md).
 
 ### Encryption
 
@@ -1211,7 +1211,7 @@ kibana:
 ##### `metadata` 
 ([Enterprise](https://readonlyrest.com/enterprise))
 
-User to define the Custom ROR Kibana Metadata which can be used in [Custom middleware](kibana#custom-middleware). The `kibana.metadata` in ReadonlyREST settings is an unstructured YAML object. 
+User to define the Custom ROR Kibana Metadata which can be used in [Custom middleware](kibana.md#custom-middleware). The `kibana.metadata` in ReadonlyREST settings is an unstructured YAML object. 
 
 It supports [dynamic variables](elasticsearch.md#dynamic-variables).
 

kibana.md

@@ -1139,7 +1139,7 @@ readonlyrest:
       signature_key: "my_shared_secret_kibana1_(min 256 chars)" # <- use environmental variables for better security!
 ```
 
-You may also use any custom claim from the OIDC `userinfo` token in ACL rules by using `{{jwt:assertion.<path_to_your_claim>}}` syntax. See the [Dynamic variables from JWT claims section](elasticsearch##usage-examples) for more information. ( **TIP** : Do not forget the `assertion` prefix in front of you jsonpath. )
+You may also use any custom claim from the OIDC `userinfo` token in ACL rules by using `{{jwt:assertion.<path_to_your_claim>}}` syntax. See the [Dynamic variables from JWT claims section](elasticsearch.md#usage-examples) for more information. ( **TIP** : Do not forget the `assertion` prefix in front of you jsonpath. )
 
 ### Kibana side