Integrating with third-party programs

To access a third-party program from Dentrix Enterprise, the user authentication process can be done using the following methods:

#1  The user enters credentials in the third-party program - The user clicks a button in DXE to launch the third-part program and then enters separate authentication credentials.

#2  Use saved user credentials in DXE to launch the third-party program - When a site registers for a third-party service, a customer identifier is saved in DXE. Also, user credentials are created by the third-party program and saved in DXE for the corresponding users in DXE. The saved information is passed to the third-party program when the user attempts to access it from DXE.

#3  Use integrated Windows authentication - The user's session context is used to identify and authenticate a Windows user by the third-party program. The user is further checked for authorization to access functionality in the third-party program. After a successful authorization, the third-party program performs the requested operation for the DXE user.

#4  Use integrated Windows authentication and OAuth 2.0 authorization - The user's Windows session context (SPNEGO) is used by an authentication server to authenticate a Windows user to the third-party program. After a successful authentication, the user's access request is checked against the user's granted scope (authorization). Then, if that is successful, an access token and a refresh token are issued to the user session. Any subsequence requests will be accompanied with the active access token.

Table 1: Current option comparison and SSO for DXE.