Your website provides a repository for yum/dnf for updating the software as described https://ltb-project.org/documentation/self-service-password/1.3/install_rpm. However, it only supports Red Hat / CentOS 7. Could you provide a package for Red Hat 8 / CentOS 8.

Additionally, when I use the earlier package it has a dependency on 'httpd'. Could this be removed as the software als

I have followed instructions for installation by downloading both versions available here https://www.pwm-project.org/artifacts/pwm/release/
1.9.0 and 1.9.1
when I try to open the webapp it redirects to pwm/private/config/config-guide
which gives a 500 error. Manually inspecting the pwm directory reveals ../private/config/ exists but not config-guide.
I then built from repo using maven and

Hello,

I'd like to ask documents which provide information to upgrade Metatron discovery and Metatron druid.
Such as, to keep the druid ingested data and permission control, which folder should back-up, etc.

Many thanks,

This part is really not nice solution, you should not create standard user for Mokey app.

1. New role is not required, there already exist 'User Administrator'
2. Don't use user, use service

$ mkdir /etc/mokey/keytab
$ kinit adminuser
$ ipa service-add mokey/server.example.com
$ ipa role-add-member 'User Administrator' --services=mokey/server.example.com@EXAMPLE.COM
$ ipa-getkeytab

request.py line 106:

the body of the post is always dumps, this means we cannot use a JSON string as the body for a POST request.

We should update this part to be able to manage both

Is your feature request related to a problem? Please describe.
Some tests are easier to write using cucumber syntax (gherkin). I think of many IT tests and e2e ends (API testing, and GUI testing).
We can configure cucumber to run such tests.

Describe the solution you'd like
Configure cucumber to run tests :)

Describe alternatives you've considered
N/A

*Additional context

Description

Update the contributors guide to add that all files need to be added to the git repo to be used in the library.

The work carried out in this issue needs to be reflected in our SOPs here and here.

Pre-requisites:
We need to know what this solution will be called once in prod

the v3 version brings many changes: The integrated help documentation needs to be re-done almost completely to match the new developments.