Discussions
Categories
- 382.3K All Categories
- 2.1K Data
- 208 Big Data Appliance
- 1.9K Data Science
- 447.9K Databases
- 220.9K General Database Discussions
- 3.7K Java and JavaScript in the Database
- 25 Multilingual Engine
- 522 MySQL Community Space
- 465 NoSQL Database
- 7.8K Oracle Database Express Edition (XE)
- 2.9K ORDS, SODA & JSON in the Database
- 490 SQLcl
- 3.9K SQL Developer Data Modeler
- 186.1K SQL & PL/SQL
- 21K SQL Developer
- 293.2K Development
- 7 Developer Projects
- 128 Programming Languages
- 289.9K Development Tools
- 96 DevOps
- 3K QA/Testing
- 645.6K Java
- 24 Java Learning Subscription
- 36.9K Database Connectivity
- 150 Java Community Process
- 104 Java 25
- 22.1K Java APIs
- 137.9K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 16 Java Essentials
- 144 Java 8 Questions
- 85.9K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.2K Java SE
- 13.8K Java Security
- 198 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 260 LiveLabs
- 36 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.8K Other Languages
- 2.3K Chinese
- 166 Deutsche Oracle Community
- 1.2K Español
- 1.9K Japanese
- 226 Portuguese
How do I connect by proxy using Visual Studio 2019 and ODT
So I have to connect by proxy with my personal account to various functional schemas. This is easy in sqlplus with syntax like
sqlplus myuser[funcschema]/[email protected]
Whilst in ODT there are proxy user and proxy password fields in the Advanced Settings for a connection, I've found no combination that works so far. I only have the single password (for my account), but the form requires that the "Password" field is populated. However, if that is completed, and the "Proxy Password" left blank I get an "ORA-01005: null password given; logon denied" error. If I use my password for BOTH, I get "ORA-01017: invalid username/password; logon denied". So am confused as how this can work. I can connect by proxy without issue in SQL*Plus and SQL*Developer.
I think the issue is that it will not allow you to leave the password field as empty - you cannot save a connection like that, but believe that should be the case in this scenario. In VS Code, there is a similar tool that allows that kind of config, and it works fine.
Answers
-
This is a bug because the password textfield is required and cannot be passed null value. However you can test the connection using a proxy user and get "connection succeeded", but not save it.
-
I believe it was a bug, so thanks for confirming that. The follow up question is how to get that formally acknowledged, such that it will be fixed in a pending release. Am also going down the support.oracle.com route with this issue, but as yet it's not been formally accepted as a bug with my SR.
-
Hi, unfortunately if you use a single-session proxy (eg no password needed for end user) you are indeed hitting a bug in that the connection dialog insists you provide a password. The bug number is 32097768.
If you use a two session proxy (eg alter user scott grant connect through scott_proxy AUTHENTICATED USING PASSWORD), then this is not an issue. However that is not nearly as commonplace as single-session proxy.
Thanks for taking the time to report this and again, my apologies.
-
Thanks for the detailed response. This "single-session proxy" is the mechanism we have to use at work, so we have no choice. I'll hope that the bug might be fixed before long.