Error "ORA-28040: No matching authentication protocol" When Using SQLNET.ALLOWED_LOGON_VERSION (Doc

Error "ORA-28040: No matching authentication protocol" When Using SQLNET.ALLOWED_LOGON_VERSION (Doc ID 755605.1)

To Bottom

---

Modified:10-Jul-2012Type:PROBLEM

In this Document

Symptoms

Changes

Cause

Solution

References

---

APPLIES TO:

JDBC - Version 10.1.0 to 10.2.0.5
Information in this document applies to any platform.

SYMPTOMS

When using the property "SQLNET.ALLOWED_LOGON_VERSION=10" set in the file sqlnet.ora on the server side, a 10g JDBC thin driver connecting to this 10g oracle database, fails with following errors:

The Network Adapter could not establish the connection 
.... 
ORA-28040: No matching authentication protocol

.

CHANGES

Configuring SQLNET.ORA on the server side.

CAUSE

BUG 6051243 - ORA-28040: WHEN LISTENER USES SQLNET.ALLOWED_LOGON_VERSION

A 10.2 thin jdbc driver is identifying itself as 8.1.5 client and hence the connection is failing with error ORA-28040: No matching authentication protocol

SOLUTION

To resolve the above issue you may implement any one of the following :- 

- Change the entry in sqlnet.ora file on the server machine: 
from: 
SQLNET.ALLOWED_LOGON_VERSION=10 

to: 
SQLNET.ALLOWED_LOGON_VERSION=8 

OR 

- Use the OCI driver instead of the THIN driver. The OCI driver identifies itself correctly as a 10.2 client and thus the connection succeeds. 

OR 

- If you are using 10.2.0.4 version of the driver then, you may download Patch:6779501 from My Oracle Support. 

OR 

- If you are using 10.1.0.5.0 version of the driver then, you may download Patch:6505927 from My Oracle Support. 

OR 

- Use JDBC 11g THIN driver.

REFERENCES

BUG:6051243 - ORA-28040: WHEN LISTENER USES SQLNET.ALLOWED_LOGON_VERSION