How To Set SQLNET.ALLOWED_LOGON To Avoid ORA-01017: Invalid Username/password; Logon Denied

(Doc ID 2414685.1)

Last updated on JULY 01, 2018

Applies to:

Oracle Database - Enterprise Edition - Version 12.2.0.1 and later
Information in this document applies to any platform.

Goal

How to avoid ORA-01017: invalid username/password error when connecting remotely to 12.2 with 11.2 client by setting adjusting SQLNET.ALLOWED_LOGON parameter

 

After install of 12.2 GI/RDBMS and created database, but when trying to connect to 12.2 database remotely and getting below errors

C:\Users\socharu>sqlplus testuser@test123

SQL*Plus: Release 11.2.0.1.0 Production on Tue May 8 12:45:24 2018

Copyright (c) 1982, 2010, Oracle. All rights reserved.

Enter password:
ERROR:
ORA-28040: No matching authentication protocol

Common recommendation is as follows for SQLNET.ALLOWED_LOGON

SQLNET.ALLOWED_LOGON_VERSION=8
SQLNET.ALLOWED_LOGON_VERSION_CLIENT=8
SQLNET.ALLOWED_LOGON_VERSION_SERVER = 10


after adding and bouncing SCAN_LISTENER and then trying to connect remotely encountering  ORA-01017: invalid username/password; logon denied, this despite there being no issue with password.

On server there is successful connection using same username/password


C:\Users\testuser>sqlplus testuser@test123

SQL*Plus: Release 11.2.0.1.0 Production on Tue May 8 14:56:54 2018

Copyright (c) 1982, 2010, Oracle. All rights reserved.

Enter password:
ERROR:
ORA-01017: invalid username/password; logon denied


FROM server
---------------

SQL> conn testuser/*******
Connected.
SQL> sho user
USER is "testuser"
SQL>

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms