Feedback
Did this article resolve your question/issue?

   

Article

Unable to connect to Oracle 12c when FIPS is enabled using Connect for ADO.Net Oracle Provider

Information

 
TitleUnable to connect to Oracle 12c when FIPS is enabled using Connect for ADO.Net Oracle Provider
URL Nameunable-to-connect-to-oracle-12c-when-fips-is-enabled-using-connect-for-ado-net-oracle-provider
Article Number000115055
EnvironmentProduct: Connect for ADO.Net
Version: 4.2
O/S: Windows
Database: Oracle 12c
Application: N/A
Question/Problem Description

Unable to connect to Oracle 12c when FIPS is enabled using Connect for ADO.Net Oracle Provider

Steps to Reproduce
Clarifying Information
Error MessageORA-01017: invalid username/password; logon denied
Defect Number66235
Enhancement Number
Cause
To connect to Oracle 12c, provider uses wire protocol version 11 which uses MD5, SHA1 and SHA 512 message digests.

All three message digests were mandated for generating encrypted password; however, MD5 is not .NET FIPS compliant and thus .Net was throwing an error.
Resolution
Fixed in hotfix 4.2.0.12617

Refer to "Connect for ADO.NET and Connect for .NET hot fix download and install instructions" for instructions on how to download and install the hot fix.
 
Workaround
Notes
Last Modified Date6/5/2017 8:41 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.