User authentication in Dragon Medical One

Dragon Medical One offers the following options for user authentication:

  • Microsoft Entra ID authentication: The user signs in by using an existing Microsoft Entra identity.

  • Native authentication: The user enters a user name and password that the administrator provides. The Nuance Management Server (NMS) checks the credentials.

  • LDAP authentication: The user enters a user name and password. An LDAP server checks the credentials.

  • Trusted authentication: The user signs in to Microsoft Windows by using their Active Directory user name and password. Dragon Medical One automatically signs the user in. The Nuance Management Server (NMS) checks the credentials.

  • SSO authentication (US only): The user is redirected to your corporate identity provider for authentication. If the user isn't signed in to the corporate identity provider domain, they're prompted for credentials. If the user is already signed in to the corporate identity provider domain, they're redirected and signed in to Dragon Medical One without being prompted for credentials.

Microsoft Entra ID authentication

This authentication method is the default configuration. Microsoft Entra ID authentication (formerly Azure Active Directory authentication) lets users sign in to Dragon Medical One by using an existing Microsoft Entra identity. A central authentication service performs authentication and interacts with Microsoft Entra to validate the user credentials. The central authentication service passes a secure token to Dragon Medical One, which then grants the user access.

Prerequisites:

  • Dragon Medical Server and Dragon Medical One are installed and running properly.

  • You have access to an account with Tenant admin permissions and an account with Entra admin permissions. These accounts can be the same or separate.

  • You have the tenant ID under which your app is registered. You can find this ID in your Azure portal.

  • On Nuance Management Center, complete the Microsoft Entra ID linking. For more information, see the Nuance Management Center Administrator Guide.

Configuring Microsoft Entra ID authentication

To grant permissions for Dragon Medical One and Dragon Medical Server and configure Microsoft Entra ID as your authentication method, complete the following steps:

  1. Go to the following URL by using your tenant admin account. Replace <EntraIdTenantId> with the tenant ID.

    https://login.microsoftonline.com/<EntraIdTenantId>/v2.0/adminconsent?client_id=932ea98f-77cd-421f-837f-e32bc5acc7e8&scope=932ea98f-77cd-421f-837fe32bc5acc7e8/.default

  2. Select Accept.

  3. Go to the following URL by using your Entra admin account. Replace <EntraIdTenantId> with the tenant ID.

    https://login.microsoftonline.com/<EntraIdTenantId>/v2.0/adminconsent?client_id=296df406-a086-4eca-9067-21d982cd8ff9&scope=296df406-a086-4eca-9067-21d982cd8ff9/.default

  4. Select Next > Accept.

    To check that you successfully granted permissions for Dragon Medical One and Dragon Medical Server, check the list of enterprise applications in your Azure portal.

  5. Open the SoD.exe.config file.

  6. In the SoD.Settings, Authentication setting, specify: <value>entraid</value>.

  7. In the SoD.Settings, EntraIdConfig setting, specify the tenant ID: <EntraIdTenantId>.

For more information and best practices for using Microsoft Entra ID, see the Microsoft Entra documentation.

Native authentication

You must create a user account in NMC before the user can sign in to Dragon Medical One. The user enters the user name and password provided by the administrator, and the credentials are sent to NMS for authentication.

Note

To enable users to reset their password if they forget it, make sure you provide their primary email address when you create the user accounts in NMC. For more information, see Creating user accounts.

Procedure:

In the SoD.exe.config file, SoD.Settings, Authentication setting, specify: <value>native</value>.

Configuring password settings in NMC

To define password expiration and complexity criteria for users of an organization, complete the following steps:

  1. Search for the organization, select and hold (or right-click) it, and select Details.

  2. On the Products tab, open the General tab, and expand Password Settings.

  3. Define the criteria.

  4. Select Password must meet complexity requirements.

  5. Select Save.

LDAP authentication

The user credentials are sent to NMS to authenticate against an LDAP server hosted in your organization. The authentication calls from Dragon Medical One to NMS go through an NMS local authenticator.

Deploying the NMS local authenticator

To deploy the on-premises NMS local authenticator, complete the following steps:

  1. Sign in to NMC with your administration credentials.

  2. On the Utilities ribbon, select Tools > Install local authenticator > Save.

  3. Copy the LocalAuthenticator.exe file from your downloads folder to the local server where you're installing it.

  4. In NMC, search for the organization, select and hold (or right-click) it, and select Details.

  5. Open the Organization Tokens tab and add a new token. Use this token to connect the local authenticator to your NMS organization.

  6. Install the local authenticator by using the organization token you generated in the previous step on a local server that's accessible to both the NMC server and your clients.

  7. Open the NMS.LocalAuthenticator.Service.exe.config file. By default, this file is in the following location: C:\Program Files\Nuance\Local Authenticator.

  8. Check that the NMS customer token is correct and the NMS server address is https://nmc-hc-prod-us.nuancehdp.com.

  9. For information about how to install an SSL certificate, see the Local Authenticator installation and configuration guide supplied with the installer.

Configuring Dragon Medical One for LDAP authentication

In the SoD.exe.config file, SoD.Settings, Authentication setting, specify <value>ldaplocal</value>.

Configuring your NMC organization for LDAP authentication

To connect Dragon Medical One with your on-premises local authenticator, complete the following steps:

  1. Search for the organization, select and hold (or right-click) it, and select Details.

  2. Open the Products tab and expand Dragon Medical Server.

  3. In the NMS on-premises server URL field, enter the URL of the on-premises NMS local authenticator, including the port that hosts the authentication interface on the local authenticator.

    • HTTP default port number: 80

    • HTTPS default port number: 443

  4. Select Save.

  5. On the Domains tab, select Add.

  6. Enter the name and the LDAP Active Directory connection string, and then select Save.

Configuring user accounts in NMC for LDAP authentication

To configure a user account for LDAP authentication, complete the following steps:

  1. Search for the user account, select and hold it (or right-click it), and select User Account Details.

  2. Open the Credentials tab.

  3. On the NTLM tab, select Add. The User name and Organization Name fields are already filled out.

  4. From the Domain list, select the domain you added earlier.

  5. In the Login field, enter the LDAP login ID.

  6. Select Save.

If a user already exists in NMS with a different NMS login ID, you need to connect the LDAP login ID and the NMS login ID. Proceed as follows:

  1. Search for the user account, select and hold it (or right-click it), and select User Account Details.

  2. Open the Credentials tab.

  3. On the Token tab, select Add and enter the LDAP login ID.

Note

If you use self-signed certificates or a signed certificate from an internal CA for authentication, you can disable CRL validation to avoid authentication errors.

Trusted authentication

NMS authenticates users by receiving their Active Directory credentials when they sign in to Microsoft Windows. Users can use Dragon Medical One without entering a user name and password, so the sign-in dialog box doesn't appear.

Authentication calls from Dragon Medical One to NMS go through an NMS local authenticator. For information about how to deploy the NMS local authenticator and configure your NMS organization, see LDAP authentication.

Configuring Dragon Medical One for trusted authentication

In the SoD.exe.config file, SoD.Settings, Authentication setting, specify: <value>trusted</value>.

Configuring user accounts in NMC for trusted authentication

To configure a user account for authentication in Active Directory, complete the following steps:

  1. Search for the user account, select and hold it (or right-click it), and select User Account Details.

  2. Open the Credentials tab.

  3. On the NTLM tab, select Add. The User name and Organization Name fields are already filled out.

  4. From the Domain list, select the user's domain.

  5. In the Login field, enter the Active Directory sign-in ID.

  6. Select Save.

Single sign-on (SSO) authentication

Note

This feature is available for Dragon Medical One in the US only.

SSO authentication enables users to sign in to Dragon Medical One by using their corporate identity, such as Windows Active Directory credentials. A central authentication service performs the authentication. This service interacts with your corporate identity provider to validate the user credentials. The central authentication service passes a secure token to Dragon Medical One, which then grants the user access. When Dragon Medical One starts, users are redirected to the corporate identity provider. If the user isn't authenticated to the corporate identity provider domain, they're prompted for credentials. If the user is authenticated to the domain, they're automatically granted access to Dragon Medical One.

Configuring SSO authentication by using Auth0

Follow these steps:

  1. Open the SoD.exe.config file.

  2. In the SoD.Settings section, set the Authentication setting to <value>sso</value>.

  3. In the SoD.Settings section, set the Domain setting to <value>nuancehdp.auth0.com</value>.

  4. In the SoD.Settings section, set the ClientId setting to <value>rtsoCXxRETvN3a0SavF6B5srHn3CXbwa</value>.

  5. In the SoD.Settings section, set the Connection setting to the connection name provided by your Nuance technical contact.

  6. In the SoD.Settings section, set the RedirectUri setting to <value>https://nuancehdpdev.auth0.com/mobile</value>.

Note

The specified values might change depending on your environment.

Configuring Dragon Medical One to require re-authentication

When users share workstations in an environment, you can configure Dragon Medical One to prompt users for their credentials every time they sign in. To enable this feature, follow these steps:

  1. Open the SoD.exe.config file.

  2. In the SoD.Settings section, add the setting ForceAuthenticationPromptOnStartup and specify the value as follows:

<setting name="ForceAuthenticationPromptOnStartup" serializeAs="String">
  <value>True</value>
</setting>
  • Last updated on