-
Notifications
You must be signed in to change notification settings - Fork 129
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
anonymous is missing the Overall/Read permission #44
Comments
Hello, I think this is an elusive race condition that we've been unable to reproduce where the init.groovy.d scripts collide with each other so the authentication stuff isn't setup correctly. Are you able to consistently recreate this problem? |
Hi Nick, Just wondering if this has been sorted yet? I consistently come across this error when using docker-toolbox (on Windows) which uses Docker version 17.05.0-ce, build 89658be. I run And when I access the page
I've tried the steps pointed out marcelloromani but the |
It hasn't been yet, no, as it's not been possible to reproduce it consistently. I span up the tools yesterday with Docker version 17.06.0-ce and didn't have this problem, so probably what needs to happen is someone looks into if there's a way the scripts can be sequenced - although that might be tricky as I think each one is run in a separate thread. |
@rbhadti94 hi, have you been able to solve it? I'm consistently getting the same error. I get it even while using Ubuntu. I've disabled every integration with ldap, Gerrit, etc. if that helps |
@MassimoSporchia That could be an option, or we have one central script that calls the others. The correct order should be to run "adop_ldap.groovy", then "role_based_auth.groovy", then "adop_general.groovy", then everything else I think - really it's just whatever order means all of the scripts run correctly and apply their changes. |
Added related issue #51 |
After starting the image as per the instructions, I accessed the web interface and the following error appeared:
I've tried disabling security in
config.xml
, but apparently that gets recreated with security enabled.The text was updated successfully, but these errors were encountered: