Feedback
Did this article resolve your question/issue?

   

Article

Connection to Salesforce fails with AUTHENTICATIONMETHOD is invalid

Information

 
TitleConnection to Salesforce fails with AUTHENTICATIONMETHOD is invalid
URL NameConnection-to-Salesforce-fails-with-AUTHENTICATIONMETHOD-is-invalid
Article Number000125011
EnvironmentProduct: Progress DataDirect for JDBC for Salesforce
Version: 6.0
OS: Java
Database: Salesforce
Application: All supported applications
Question/Problem Description
Connection to Salesforce using the Progress DataDirect for JDBC for Salesforce fails with AUTHENTICATIONMETHOD is invalid
Steps to Reproduce
Clarifying Information
Connection was working fine, than a patch was applied.
Error Message[DataDirect][SForce JDBC Driver][SForce]The value of none for connection option Connection.
Defect Number
Enhancement Number
Cause
With the implimentation of OAUTH the driver no longer writes the value of AUTHENTICATIONMETHOD to native files.
Resolution
Add the following parameter to the connection URL, CreateMap=ForceNew and make a new connection. 
For example:
jdbc:datadirect:sforce://login.salesforce.com;User=xxxxxx;Password=xxxxxx;CreateMap=ForceNew....

This will rebuild the local schema files. Once a connection has been established the connection parameter can be removed.
Workaround
Notes
Last Modified Date7/23/2019 6:52 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.