- 3,716,134 Users
- 2,242,961 Discussions
- 7,845,841 Comments
Forum Stats
Discussions
Categories
- 17 Data
- 362.2K Big Data Appliance
- 7 Data Science
- 1.6K Databases
- 479 General Database Discussions
- 3.7K Java and JavaScript in the Database
- 22 Multilingual Engine
- 487 MySQL Community Space
- 5 NoSQL Database
- 7.6K Oracle Database Express Edition (XE)
- 2.8K ORDS, SODA & JSON in the Database
- 417 SQLcl
- 42 SQL Developer Data Modeler
- 184.9K SQL & PL/SQL
- 21K SQL Developer
- 1.9K Development
- 3 Developer Projects
- 32 Programming Languages
- 135.1K Development Tools
- 9 DevOps
- 3K QA/Testing
- 259 Java
- 6 Java Learning Subscription
- 11 Database Connectivity
- 67 Java Community Process
- 1 Java 25
- 9 Java APIs
- 141.1K Java Development Tools
- 6 Java EE (Java Enterprise Edition)
- 153K Java Essentials
- 135 Java 8 Questions
- 86.2K Java Programming
- 270 Java Lambda MOOC
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 10 Java SE
- 13.8K Java Security
- 3 Java User Groups
- 22 JavaScript - Nashorn
- 18 Programs
- 125 LiveLabs
- 31 Workshops
- 9 Software
- 3 Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 4 Deutsche Oracle Community
- 11 Español
- 1.9K Japanese
- 2 Portuguese
.Net ManagedDataAccess fails to connect using Windows Native Authentication
We're trying to connect to Oracle database using .Net ManagedDataAccess (Nuget package Oracle.ManagedDataAccess 19.3.0) and Windows Native Authentication, but database responds with ORA-01017: invalid username/password; login denied
Connecting with same user via SqlPlus works without problem
Both machines have windows os and belong to same domain
All 3 steps according to 3.3.8 Using Windows Native Authentication (NTS) are done (https://docs.oracle.com/en/database/oracle/oracle-data-access-components/18.3/odpnt/featConnecting.html#GUID-51D1ADDB-D6… )
External user created in oracle database with domain name
On Client side:
Connection string has User Id=/
SQLNET.AUTHENTICATION_SERVICES is set to (NTS)
Client Trace:
TID:1 (CFG) (VER) Oracle Data Provider for .NET, Managed Driver Version : 4.122.19.1
TID:1 (CFG) (VER) Oracle Data Provider for .NET, Managed Driver Informational Version : 4.122.19.1:20190510
TID:1 (CFG) (.NET) SQLNET.AUTHENTICATION_SERVICES : (NTS)
Oracle database trace shows failed logon attempt with username that doesn't contain domain name.
Using Oracle.ManagedDataAccess.Core 2.19.3 for our core apps results in same error (also logged on oracle database trace as user without domain name).
Is there something else that has to be done to make it work?
Answers
-
Are you using NTLM or Kerberos? Only the former is supported in managed ODP.NET.
-
We are using NTLM
-
Is it working for anyone when using domain name or is it a bug?
On client
SQLNET.AUTHENTICATION_SERVICES is set to (NTS), using NTLM
On server
OSAUTH_PREFIX_DOMAIN is default (true) and user created with domain name
-
Sounds like a bug as you appear to have everything correctly set. I would recommend opening up a service request with Oracle Support to find the root cause so that the bug can be fixed.