We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Here I am going to outline what the test coverage will be,.
request
Rinse and repeat test with hash coming from within settings.json (and not from the file system)
The new users blob will look like this:
"users": { "admin": {"is_admin": true, "hash": "$2a$10$WQ/wvL2pzJlIgCP719JnLOr0zpsYpWWjT3yQdVq37XlfbV6DJaHCy" }, "user": {"is_admin": false, "hash": "$2a$10$TQrVqy4eRpG7Kde7Sfl8..eycP3Bc/K.2vlDFY1u9C0Stl24.8V3G" } }
admin has the password of password and user as password2
password
password2
The file system will be a bit more involved with a settings blob of
"ep_hash_auth": { "hash_typ": "sha512", "hash_dig": "hex", "hash_dir": "/var/etherpad/users", "hash_ext": "/.hash", "hash_adm": false, "displayname_ext": "/.displayname" },
then we will have to create the folder structure and create
/var/etherpad/users/admin/.hash
and
/var/etherpad/users/user/.hash
with each .hash file containing the hash of each user.
.hash
The text was updated successfully, but these errors were encountered:
I wrote an example test that works that can be used for reference :)
Sorry, something went wrong.
No branches or pull requests
Here I am going to outline what the test coverage will be,.
request
try to auth against /admin with them set (test for failure and success)Rinse and repeat test with hash coming from within settings.json (and not from the file system)
The new users blob will look like this:
admin has the password of
password
and user aspassword2
The file system will be a bit more involved with a settings blob of
then we will have to create the folder structure and create
and
with each
.hash
file containing the hash of each user.The text was updated successfully, but these errors were encountered: