Choose an Authentication Type

Mirth® Connect by NextGen Healthcare User Guide

Code Template Contexts

Similar to how a code template library can be included only on specific channels, code templates can further be isolated to specific scripts. This can be helpful for ensuring that there are no conflicts between function names, and also for better memory usage, since not all code templates need to be compiled in with all scripts across your entire server. The script contexts are organized into groups, allowing you to easily include a code template in, for example, all global scripts, in a single select. The following groups are displayed: Global Scripts: The global deploy/undeploy/preprocessor/postprocessor scripts, not specific to any particular channel. For additional information, see Edit Global Scripts View. Channel Scripts: The channel-level deploy/undeploy/preprocessor/postprocessor scripts (more info here) , as well as the JavaScript Attachment Handler and JavaScript Batch Adapter (for additional information, see Data Types) . Source Connector: The source filter/transformer scrip

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

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

Basic HTTP Authentication

Provides Basic Authentication support for HTTP-based source connectors. 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. Parent topic: HTTP Authentication Settings

Mirth® Connect by NextGen Healthcare User Guide

OAuth 2.0 Token Verification

This feature performs a GET request to an external HTTP endpoint, passing an OAuth access token as either a request header or query parameter. If the response code from this endpoint is >= 400, the request will be rejected and not processed through the channel. Item Name Description A Access Token Location Determines where the access token is located in client requests. Request Header: The field to the right specifies the HTTP header to pull the access token from. This same header will be sent in the request to the verification URL. Query Parameter: The field to the right specifies the query parameter to pull the access token from. This same parameter will be sent in the request to the verification URL. B Verification URL The HTTP URL to perform a GET request to for access token verification. If the response code is >= 400, the authentication attempt is rejected by the server, and the request will not be processed through the channel. Note: This token verification feature does not cons

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

Choose an Authentication Type

Recommendations

Code Template Contexts

Custom Java Class HTTP Authentication

Digest HTTP Authentication

Basic HTTP Authentication

OAuth 2.0 Token Verification

JavaScript HTTP Authentication

Choose an Authentication Type

Code Template Contexts

Custom Java Class HTTP Authentication

Digest HTTP Authentication

Basic HTTP Authentication

OAuth 2.0 Token Verification

JavaScript HTTP Authentication