trouble
November 27, 2018, 9:05am
1
Hi
I had been playing with my RoR config today, and now when i press save in the RoR UI to save the config, i am seeing in the log files the following line before each JWT rule
[2018-11-27T07:00:44,298][ERROR][t.b.r.a.b.r.i.JwtAuthSyncRule] HS256 KeyFactory not available
Can anyone help tell me what is causing this?
Thanks
sscarduzio
November 27, 2018, 10:40am
2
Hi Paul, please use either of RSA, HMAC, EC, or NONE as algorithm in your YAML. See the docs:
# For Elasticsearch
## Overview: The ReadonlyREST Suite
ReadonlyREST is a light weight Elasticsearch plugin that adds encryption, authentication, authorization and access control capabilities to Elasticsearch embedded REST API. The core of this plugin is an ACL engine that checks each incoming request through a sequence of **rules** a bit like a firewall. There are a dozen rules that can be grouped in sequences of blocks and form a powerful representation of a logic chain.
The Elasticsearch plugin known as `ReadonlyREST Free` is released under the GPLv3 license, or alternatively, a commercial license \(see [ReadonlyREST Embedded](https://readonlyrest.com/embedded)\) and lays the technological foundations for the companion Kibana plugin which is released in two versions: [ReadonlyREST PRO](https://readonlyrest.com/pro) and [ReadonlyREST Enterprise](https://readonlyrest.com/enterprise).
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.
### ReadonlyREST Free plugin for Elasticsearch
In this document we are going to describe how to operate the Elasticsearch plugin in all its features. Once installed, this plugin will greatly extend the Elasticsearch HTTP API \(port 9200\), adding numerous extra capabilities:
* **Encryption**: transform the Elasticsearch API from HTTP to HTTPS
* **Authentication**: require credentials
* **Authorization**: declare groups of users, permissions and partial access to indices.
* **Access control**: complex logic can be modeled using an ACL \(access control list\) written in YAML.
show original