ORA-28040 No matching authentication protocol exception

Question

I am trying to connect my grails project to Oracle databse Oracle 12c  in windows 8  system  However  whenever I run my application I get following exception    Caused by  org apache commons dbcp SQLNestedException   Cannot create PoolableConnectionFactory  ORA-28040   No matching authentication protocol   Caused by   java sql SQLException  ORA-28040   No matching authentication protocol   According to internet suggestion I also tried editing my    ora file but it is not working   I added following snippet in sqlnet ora file    SQLNET ALLOWED LOGON VERSION 10 SQLNET ALLOWED LOGON VERSION CLIENT 10 SQLNET ALLOWED LOGON VERSION SERVER 10   Here i tried assigning  10 11 12  but neither of them is working   Can anyone please help me with this

User · Answer

just install ojdbc-full  That contains the 12 1 0 1 release

User · Answer

Here is some text I found at experts-exchange      Bug 14575666      In 12 1  the default value for the SQLNET ALLOWED LOGON VERSION   parameter has been updated to 11  This means that database clients   using pre-11g JDBC thin drivers cannot authenticate to 12 1 database   servers unless theSQLNET ALLOWED LOGON VERSION parameter is set to the   old default of 8       This will cause a 10 2 0 5 Oracle RAC database creation using DBCA to   fail with the ORA-28040  No matching authentication protocol error in   12 1 Oracle ASM and Oracle Grid Infrastructure environments       Workaround   Set SQLNET ALLOWED LOGON VERSION 8 in the   oracle network admin sqlnet ora file

User · Answer

Except for adding the following to sqlnet ora  SQLNET ALLOWED LOGON VERSION CLIENT   8 SQLNET ALLOWED LOGON VERSION SERVER   8   I also added the following to both the Client and Server  which resolved my issue  SQLNET AUTHENTICATION SERVICES    NONE    Also see post ORA-28040  No matching authentication protocol

User · Answer

I was using eclipse and after trying all the other answers it didn t work for me   In the end  what worked for me was moving the ojdb7 jar to top in the Build Path  This occurs when multiple jars have conflicting same classes         Select project in Project Explorer   Right click on Project - gt  Build Path - gt  Configure Build Path   Go to Order and Export tab and select ojdbc jar   Click button TOP to move it to top

User · Answer

Adding   SQLNET ALLOWED LOGON VERSION SERVER   8   is the perfect solution sql ora directory     product 12 1 0 dbhome 1 NETWORK ADMIN

User · Answer

While for most cases replacing ojdbc driver jar will be the solution  my case was different    If you are certain you are using correct ojdbc driver  Double check if you are actually connecting to the database you are thinking you are  In my case jdbc configuration  in Tomcat conf  was pointing to different database that had different Oracle version

User · Answer

My Initial error is   ORA-28040  No matching authentication protocol exception  My DB version is 12 2  Solaris  and client version is 11 2   windows   I have added below in both server and client sqlnet ora  SQLNET ALLOWED LOGON VERSION CLIENT   8 SQLNET ALLOWED LOGON VERSION SERVER   8  while connecting  I have got invalid username and password hence I have recreated the password   same password   in database which is resolved my issue

User · Answer

This except for adding the following to sqlnet ora  SQLNET ALLOWED LOGON VERSION CLIENT   8 SQLNET ALLOWED LOGON VERSION SERVER   8   If you get  ORA-01017  invalid username password  logon denied  error  then you need to re-create your password

User · Answer

Very old question but providing some additional information which may help someone else  I also encountered same error and I was using ojdbc14 jar with 12 1 0 2 Oracle Database  On Oracle official web page this information is listed that which version supports which database drivers  Here is the link and it appears that with Oracle 12c and Java 7 or 8 the correct version is ojdbc7 jar  In the ojdbc6 jar is for 11 2 0 4

User · Answer

I resolved this issue by using ojdbc8 jar   Oracle 12c is compatible with ojdbc8 jar

User · Answer

I deleted the ojdbc14 jar file and used ojdbc6 jar instead and it worked for me

[oracle] ORA-28040: No matching authentication protocol exception

Examples related to oracle

Examples related to oracle12c