Authentication on EDC and ADC connections
- Last Updated: June 18, 2020
- 1 minute read
- Corticon
- Documentation
When you choose to create an EDC or ADC Datasource, its tab in the Vocabulary lets you specify the authentication you will require. The Database Server you select for the Datasource lists its available authentication options on the Authentication dropdown.
Most database servers allow two Authentication options:
- Basic: When available, the
Basicoption is pre-selected, and the Username and Password fields are displayed, enabled, and required. - Kerberos: Many database drivers offer Kerberos support. If your target Database Server is in a Kerberos realm, you need to ensure that you have proper target session keys. See How to enable Kerberos Authentication in Studio and Server for more information. When you select that option, the username and password fields are not available.
The Microsoft Dynamics 365 driver has three Authentication options:
- None: When a Dynamics Datasource
requires no authentication, it is appropriate for accessing public data, such as
weather information.
Noneis the default setting. - OAuth2: Uses authorization tokens to
prove an identity without giving away your password. When you choose the
OAuth2option, you need to specify the Client ID, Token URI, Client Secret, and Refresh Token for the connection. - NTLM: Uses challenge/response authentication that allows a client to prove its identity without sending a password to the server. The Username, Password, and Domain fields are required entries.