File

mod_tokenauth: Add 'purpose' constraint This allows tokens to be tied to specific purposes/protocols. For example, we shouldn't (without specific consideration) allow an OAuth token to be dropped into a slot expecting a FAST token. While FAST doesn't currently use mod_tokenauth, it and others may do in the future. It's better to be explicit about what kind of token code is issuing or expecting.

return {
  _all = {
  },
  default = {
    ["exclude-tags"] = "mod_bosh,storage,SLOW";
  };
  bosh = {
    tags = "mod_bosh";
  };
  storage = {
    tags = "storage";
  };
}