You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
global auth for all sites is not disabled after deleting user #34
when creating a new global auth user i.e "ee auth create global" it password protects all sites. deleting the new user does not deactivate the password prompt on all sites. on https://easyengine.io/commands/auth/delete/ it says use the command below but it does not work
Remove global auth on all sites (but not admin tools) with default username(easyengine)
$ ee auth delete example.com --site
Error: Parameter errors:
unknown --site parameter
I found a workaround by running ee global auth delete (this deletes all users and generates a new auth for ee-admin tools) after you will need to create a new auth for any site on the server i.e "ee auth create example.com" and then delete "ee auth delete example.com"
these steps remove the password prompt from all sites.
@aronwp to remove the global auth the syntax is ee auth delete global. The syntax in handbook is outdated. Thank you for noticing and reporting the issue. This will be fixed asap.
@mrrobot47 thanks but it's still not working correctly. The ee auth delete global command deletes the global auth user but the password box still appears on all sites. The only way to remove global auth from sites is after ee auth delete global need to run ee auth create example.com and then ee auth delete example.com and then the password box is removed from all sites.
Basically the ee auth delete global removes the user but not the htpasswd for global auth
Since both HTTP Auth and IP Whitelisting are implemented in similar way the above problem can also occur in case of removing global ip whitelisting from the site using ee auth delete global --ip
Steps to produce the issue :-
Ensure site specific ip whitelisting or add using below command :- ee auth create example.test --ip=1.1.1.1(this creates example.test_acl)
Ensure global ip whitelisting or add using below command :- ee auth create global --ip=8.8.8.8(this creates default_acl)
Now when we remove site specific ip whitelisting ee auth delete example.test --ip(updates example.test_acl)
and then remove global ip whitelisting ee auth delete global --ip(deletes default_acl)
the global ip whitelisting is not removed from the site example.test
because the site specific ip whitelisting file example.test_acl remains undeleted
Since both HTTP Auth and IP Whitelisting are implemented in similar way the above problem can also occur in case of removing global ip whitelisting from the site using ee auth delete global --ip
Steps to produce the issue :-
Ensure site specific ip whitelisting or add using below command :- ee auth create example.test --ip=1.1.1.1(this creates example.test_acl)
Ensure global ip whitelisting or add using below command :- ee auth create global --ip=8.8.8.8(this creates default_acl)
Now when we remove site specific ip whitelisting ee auth delete example.test --ip(updates example.test_acl)
and then remove global ip whitelisting ee auth delete global --ip(deletes default_acl)
the global ip whitelisting is not removed from the site example.test because the site specific ip whitelisting file example.test_acl remains undeleted
Thanks for the report, and sorry this stayed open so long. It's fixed in two steps, and both are in the current release, EasyEngine v4.13.2.
EasyEngine v4.13.0 (auth-command#57) removes a site's auth files once it has no users or whitelisted IPs of its own, so ee auth delete global and ee auth delete global --ip now remove the protection from every site without auth of its own. Before, those files kept the old global users and IPs, which is why creating and deleting a site auth worked around it.
v4.13.2 (auth-command#60) keeps the admin-tools login separate from the global auth. ee auth create global no longer turns the admin-tools user into a global user, so deleting your global users no longer leaves that one protecting the sites, and ee auth delete global no longer replaces the admin-tools password.
If an older version already moved the admin-tools user (easyengine) into the global auth, ee auth list global shows it, and on a server with admin-tools enabled ee auth delete global hands it back to admin-tools with the same password.
The syntax to remove the global auth is ee auth delete global (or ee auth delete global --user=<name> for one user).
Please update with ee cli update, and reopen this if you still see it.
Activity
mrrobot47 commentedon Nov 30, 2018
@aronwp to remove the global auth the syntax is
ee auth delete global. The syntax in handbook is outdated. Thank you for noticing and reporting the issue. This will be fixed asap.aronwp commentedon Nov 30, 2018
@mrrobot47 thanks but it's still not working correctly. The
ee auth delete globalcommand deletes the global auth user but the password box still appears on all sites. The only way to remove global auth from sites is afteree auth delete globalneed to runee auth create example.comand thenee auth delete example.comand then the password box is removed from all sites.Basically the
ee auth delete globalremoves the user but not the htpasswd for global authmbtamuli commentedon Nov 30, 2018
@mrrobot47 This looks like a problem. Reopening this issue. Let's investigate the cause of this issue and fix it.
PiyushKhurana commentedon Oct 11, 2021
Since both
HTTP AuthandIP Whitelistingare implemented in similar way the above problem can also occur in case of removing global ip whitelisting from the site usingee auth delete global --ipSteps to produce the issue :-
ee auth create example.test --ip=1.1.1.1(this creates example.test_acl)ee auth create global --ip=8.8.8.8(this creates default_acl)ee auth delete example.test --ip(updates example.test_acl)ee auth delete global --ip(deletes default_acl)the global ip whitelisting is not removed from the site
example.testbecause the site specific ip whitelisting
file example.test_aclremains undeletedPiyushKhurana commentedon Oct 11, 2021
PR updated #53
Fix here 46571f7
mrrobot47 commentedon Oct 15, 2026
Thanks for the report, and sorry this stayed open so long. It's fixed in two steps, and both are in the current release, EasyEngine v4.13.2.
EasyEngine v4.13.0 (auth-command#57) removes a site's auth files once it has no users or whitelisted IPs of its own, so
ee auth delete globalandee auth delete global --ipnow remove the protection from every site without auth of its own. Before, those files kept the old global users and IPs, which is why creating and deleting a site auth worked around it.v4.13.2 (auth-command#60) keeps the admin-tools login separate from the global auth.
ee auth create globalno longer turns the admin-tools user into a global user, so deleting your global users no longer leaves that one protecting the sites, andee auth delete globalno longer replaces the admin-tools password.If an older version already moved the admin-tools user (
easyengine) into the global auth,ee auth list globalshows it, and on a server with admin-tools enabledee auth delete globalhands it back to admin-tools with the same password.The syntax to remove the global auth is
ee auth delete global(oree auth delete global --user=<name>for one user).Please update with
ee cli update, and reopen this if you still see it.