-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
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
Possible regression of #292 #329
Comments
Here's the node record, if that's useful (probably not...):
|
Not sure if this fixes the above problem, but I patched the latest version (0.9.23) to fix a bug that did not create new admin users that were in the config file. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is with shock 0.9.21 pulled from the docker image obtained via
docker pull mgrast/shock
Background: #292
It appears, unless I'm doing something incorrectly, that now even restarting shock doesn't result in the proper permissions being given to admin users:
Conf:
First start:
kbasetest2 is not recognized as an admin:
After restarting shock, kbasetest2 is still not recognized as an admin:
Is there something I'm missing here? I can't seem to get an admin account working.
The text was updated successfully, but these errors were encountered: