build.py now supports X-Tokens. If token, username, and password are present, the token will be used. Modified config.default.json to include a token entry instead of username and password, and removed references to entries in documentation book, which were replaced by auth-token setup instructions. Basic access authentication still supported by build.py and these changes will not affect existing users.
Reasoning:
This announcement last year provided auth tokens as an alternative to basic access authentication for access to screeps user endpoints. In February, basic access authentication was removed, with the exception of the /api/user/code/ endpoint, which is why build.py remains unaffected.
The discussion here posed good points for keeping basic access around for code pushing, and I agree users should have a choice in what authentication method they use. However, I also feel using tokens over usernames and password is inherently more secure and should be supported over usernames and passwords going forward.
build.pynow supports X-Tokens. If token, username, and password are present, the token will be used. Modifiedconfig.default.jsonto include atokenentry instead ofusernameandpassword, and removed references to entries in documentation book, which were replaced by auth-token setup instructions. Basic access authentication still supported bybuild.pyand these changes will not affect existing users.Reasoning: This announcement last year provided auth tokens as an alternative to basic access authentication for access to screeps user endpoints. In February, basic access authentication was removed, with the exception of the
/api/user/code/endpoint, which is whybuild.pyremains unaffected.The discussion here posed good points for keeping basic access around for code pushing, and I agree users should have a choice in what authentication method they use. However, I also feel using tokens over usernames and password is inherently more secure and should be supported over usernames and passwords going forward.