MIRTH-3840: Added new connector plugin properties for HTTP authentication. There is a new Authenticator abstract class that gets extended for each type, and a provider/factory used by the HTTP/WS source connectors to create Authenticator implementations.
MIRTH-3841: Added Basic authentication mode. Properties include the realm and user/pass credentials. For the Web Service Listener, the previous credentials table has been moved here, and the properties will migrate as such to 3.4.
MIRTH-3842: Added Digest authentication mode. Users can set the realm, algorithms, quality-of-protection modes, opaque string, and actual user/pass credentials. An Authenticator implementation on the backend allows for all these options, much moreso than the stock Jetty authenticator allows.
MIRTH-3844: Added custom Java class authentication mode. Users can set the class name and an optional map of properties that are passed into the constructor of the Authenticator implementation.
MIRTH-3845: Added OAuth token verification mode. Mirth Connect does *not* act as a resource server or resource owner here. It is more of a passthrough client that simply hits a verification endpoint, passing along the access token. Users can decide whether the access token is expected as a request header (e.g. Authorization) or a query parameter (e.g. auth_token). Upon request, the authenticator will perform a GET request to the verification endpoint, and based solely on the response code will either accept or reject the request. If rejected, the originating system is expected to request a new access token from the resource server and then submit a new request to the channel.