When we access the binderhub's REST API under /build, there is a build_token that can be relevant to understand more about. This issue represents a summary of insights about it, and can be closed when we understand this well enough and have captured that understanding in the issue. The issue can then be used to write documentation if we conclude its relevant to document this as well.
When we access the binderhub's REST API under
/build, there is abuild_tokenthat can be relevant to understand more about. This issue represents a summary of insights about it, and can be closed when we understand this well enough and have captured that understanding in the issue. The issue can then be used to write documentation if we conclude its relevant to document this as well./buildendpoint is handled by a tornado web request handler, which is considering if its passed abuild_token. If it is passed a token, it has to be valid still./v2endpoint is handled by a tornado web request handler, that creates a build_token. This is the only place its being created.build_tokenwas introduced in add build token, apply rate limit by request ip jupyterhub/binderhub#1309