Web Dashboard

Multi-Factor Authentication User Guide

Client API Integrations

If you have built any custom integrations that use the REST API and require automatic, programmatic access, most likely you will want to exclude the user tied with the integration from MFA. No additional development is needed. See Excluding Users from MFA. If your custom integration still interacts with the user, you can elect to handle the multifactor signatures and codes manually. Because of the nature of multifactor authentication, Basic HTTP Auth is not supported when MFA is enabled. Instead invoke the /users/_login and /users/_logout endpoints to perform session-based auth. Using the TOTP API Integration Using the TOTP API integration. Using the Duo API Integration Using the Duo Universal API Integration Using the Duo Universal API integration Parent topic: Limitations of MFA

Multi-Factor Authentication User Guide

Client API Browser

You can still access the Client API documentation and browse the various methods available. However, logging in and testing operations from this browser using an MFA-enabled user is not yet supported. However, if the user is excluded from MFA, see Excluding Users from MFA, then that user will still be able to log on and perform actions here. Mirth Connect window with sign in fields and links to documentation Parent topic: Limitations of MFA

Multi-Factor Authentication User Guide

Excluding Users from MFA

You may have users that need to be able to authenticate without going through MFA. For example, a custom integration against the REST API. An administrator can exclude users from the MFA settings tab. MFA Required column for users in Multi-Factor Authentication Settings section This is available in both TOTP and Duo modes. Note that in the case of Duo, you can also set a user to "bypass" mode in the Duo Admin Panel. The user will be able to login without using a secondary device. However since communication still needs to be made to Duo even in bypass mode, depending on the integration you may need to exclude the user here on the MFA settings tab instead.

Multi-Factor Authentication User Guide

Limitations of MFA

When multi-factor authentication is enabled, certain features in Mirth® Connect by NextGen Healthcare are currently not supported. In future improvements to this extension, NextGen Healthcare will add this support where applicable. Web Dashboard Client API Browser Client API Integrations

Mirth® Connect by NextGen Healthcare User Guide

The Web Dashboard

The Web Dashboard is a quick and easy way to view channel / connector statistics across your server without needing to launch the Administrator. It runs in a web browser, and is also supported on mobile devices. To login to the Web Dashboard: In the address field of your browser, type localhost: followed by the Web Start Port number. (See the Server Manager - Server page; default: 8080. ) Select the Access Secure Site button for Web Dashboard Sign in, the page changes, prompting you to enter a Username and Password. Image of the Web Dashboard to view channel and connector statistics After you log on, you can see all of your deployed channels in a table. To view connector-level statistics, expand the arrow next to your channel name. You can also switch between current and lifetime statistics. Image of the Dashboard Statistics page to view channel statistics. To launch the Administrator interface from the Web Dashboard, select the arrow next to the user avatar in the top-right, and selec

Mirth® Connect by NextGen Healthcare User Guide

Navigation

From the Dashboard From the Channels View From the Dashboard From the Channels View Parent topic: Message Browser View

Web Dashboard

Recommendations

Client API Integrations

Client API Browser

Excluding Users from MFA

Limitations of MFA

The Web Dashboard

Navigation

Client API Integrations

Client API Browser

Excluding Users from MFA

Limitations of MFA

The Web Dashboard

Navigation