Add auth filters to handle actually checking the API Key and Tyler Ports #285
Description
Partially started in https://github.com/SuffolkLITLab/EfileProxyServer/tree/misc_refactors.
Make a ContainerRequestFilter (with an injected / @Context ResourceInfo setter func) using NameBinding to actually read in the API Key and check our database, instead of having to rely on a no-op check later in each individual endpoint.
That filter should also:
- set the Security Context to have the "Principal" be the server logging in
- could also be the Tyler user, but 1) we never actually logged them in, that only happens on the Tyler side, 2) we can only have one
- Put various User Ports that are required for the calls (i.e. what you get from the ResourceInfo / Annonation checks) to the
ResourceContext, where they can be injected in each method where they're needed.
Requires the filter to have strong knowledge of what jurisdictions are active, so should be done after #284.