Basic HTTP Authentication

Item	Name	Description
A	Realm	The protection space for this server.
B	Use Table	Use Table: When selected, use the Credentials table (B) to populate credentials. To Use the Table Select New Double-click the Username field and enter a username for the credential. Double-click the Password field and enter a password for the credential. Note: At least one username/password pair is required for the credentials. Use Map: When selected, the Java map specified by the following variable will is used to populate credentials. The map must have String keys and either String or List<String> values.

Mirth® Connect by NextGen Healthcare User Guide

Digest HTTP Authentication

Provides Digest Authentication support for HTTP-based source connectors. Item Name Description A Realm The protection space for this server. B Algorithms Specifies the digest algorithms supported by this server. MD5: The security data A1 contains the username, realm, and password. MD5-sess: The security data A1 will also contain the server and client nonces. Both: Both MD5 and MD5-sess. C QOP Modes The quality of protection modes to support. auth: Regular authentication with client nonce and count in the digest. auth-int: Same as auth (regular authentication), but also with message integrity protection enabled. D Opaque A string of data that should be returned by the client unchanged. Velocity Variable Replacement is supported in this field. The default value, ${UUID}, means that a randomly generated universally unique identifier will be sent back on each digest challenge. E Credentials Use Table: When selected, use the Credentials table (E) to populate credentials. To Use the Table Se

Mirth® Connect by NextGen Healthcare User Guide

Choose an Authentication Type

Select an option from the drop-down window. Once an HTTP Authentication type is selected, fields associated with the type appear. For additional information on each HTTP Authentication type, select a links below. Basic HTTP Authentication Digest HTTP Authentication JavaScript HTTP Authentication Custom Java Class HTTP Authentication OAuth 2.0 Token Verification Parent topic: HTTP Authentication Settings

Mirth® Connect by NextGen Healthcare User Guide

Custom Java Class HTTP Authentication

This authentication method gives you full control by allowing you to specify your own custom-developed Authenticator implementation. Item Name Description A Class Name The fully-qualified Java class name of the Authenticator class to use. B Properties Custom string properties to pass into your class. Parent topic: HTTP Authentication Settings

Mirth® Connect by NextGen Healthcare User Guide

JavaScript HTTP Authentication

Allows you to authenticate users with a custom JavaScript script. With this script you have access to source map variables, and can choose whether to send a challenged or failure response back to the client. The default script simply allows all requests to pass. The Script field will show <Default Script Set> if the default script is currently being used. If you have made any modification to the script, the Script field will show <Custom Script Set>. Select the Script field to edit the JavaScript: This script expects either a boolean ( true to accept the request, false to send back a failure response) or an AuthenticationResult object to be returned (for additional information, see User API) . There are three types of results you can return: AuthenticationResult.Success(): The request will be accepted and processed through the channel. AuthenticationResult.Challenged(authenticateHeader): The request will not be processed through the channel. A 401 response will be sent back to the clie

Mirth® Connect by NextGen Healthcare User Guide

HTTP Authentication Settings

The HTTP Authentication Settings provide automatic user authentication with a variety of supported mechanisms. for HTTP-based source connectors. Choose an Authentication Type Basic HTTP Authentication Digest HTTP Authentication JavaScript HTTP Authentication Custom Java Class HTTP Authentication OAuth 2.0 Token Verification Parent topic: Source Tab

Mirth® Connect by NextGen Healthcare User Guide

Authentication

Mirth® Connect supports both session-based cookie authentication and basic authentication. Basic Authentication: Simply include an Authorization header on all API requests, with basic credentials. Example (for admin/admin): Authorization: Basic YWRtaW46YWRtaW4= Session-Based Authentication: First, invoke the POST /users/_login endpoint, passing in your login credentials. If successful, the server will respond with a cookie (Set-Cookie header) like the following: Set-Cookie: JSESSIONID=uysqrtx9lle36ernybizstps;Path=/api;Secure Invoke the actual API endpoints of your choice, passing in the same cookie as a header: Cookie: JSESSIONID=uysqrtx9lle36ernybizstps;Path=/api;Secure Once you are done, make sure to call the POST /users/_logout endpoint, making sure to pass in the same cookie. Session-based Authentication is preferred since you only need to transmit your login credentials once. Note that the API documentation page invokes the same endpoint automatically when you login at the top: I

Basic HTTP Authentication

Recommendations

Digest HTTP Authentication

Choose an Authentication Type

Custom Java Class HTTP Authentication

JavaScript HTTP Authentication

HTTP Authentication Settings

Authentication

Basic HTTP Authentication

Digest HTTP Authentication

Choose an Authentication Type

Custom Java Class HTTP Authentication

JavaScript HTTP Authentication

HTTP Authentication Settings

Authentication