# ee auth create example.com --user=test --pass=test
# ee auth list example.com (Lists users)
# ee auth delete example.com --user=test
# ee auth update example.com --user=test --pass=mylongpassword
# ee auth whitelist create example.com --ip=1.1.1.1,2.2.2.2,3.0.0.0/8
(Future improvement can be export and import csv list of IPs)
# ee auth whitelist append example.com --ip=4.4.4.4,5.0.0.0/8
# ee auth whitelist remove example.com --ip=[2.2.2.2|all]
# ee auth whitelist list example.com (List IPs)
Global
# ee auth create global --user=test --pass=test
# ee auth whitelist global --ip=1.1.1.1,2.2.2.2,3.0.0.0/8
# ee auth list global (Lists users)
# ee auth delete global --user=test
# ee auth update global --user=test --pass=mylongpassword
# ee auth whitelist create global --ip=1.1.1.1,2.2.2.2,3.0.0.0/8
(Future improvement can be export and import csv list of IPs)
# ee auth whitelist append global --ip=4.4.4.4,5.0.0.0/8
# ee auth whitelist remove global --ip=[2.2.2.2|all]
# ee auth whitelist list global (List IPs)
Also, if you have a global auth set up, creating a site specific auth will override the global one.
Also, instead of using ee secure command like EasyEngine v3, maybe using ee auth makes more sense.
Site specific
Global
Also, if you have a global auth set up, creating a site specific auth will override the global one.
Also, instead of using
ee secure
command like EasyEngine v3, maybe usingee auth
makes more sense.