Discussions
Categories
- 196.8K All Categories
- 2.2K Data
- 238 Big Data Appliance
- 1.9K Data Science
- 450.2K Databases
- 221.7K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 550 MySQL Community Space
- 478 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 544 SQLcl
- 4K SQL Developer Data Modeler
- 187K SQL & PL/SQL
- 21.3K SQL Developer
- 295.8K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.5K Development Tools
- 107 DevOps
- 3.1K QA/Testing
- 646K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 154 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 18 Java Essentials
- 160 Java 8 Questions
- 86K Java Programming
- 80 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 204 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 437 LiveLabs
- 38 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 171 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 232 Portuguese
Vault Issues
Hi,
I am loving the vault integration - it helps speed up my workflow and interactive scripting. However, I am seeing a few issues:
- It only works with a local vault at http://127.0.0.1:8200. Whenever I point it to a remote one, after logging in and verifying my connection, I get 400 errors when SQLcl tries to access the vault.
- When I log via the vault, it is not reading the login.sql script.
- Also, when I am logged in via the vault, the history command doesn't work. It picks up previous history but no longer records new commands to it, even when I set the history limit.
Anyway, lmk if there's a workaround or where I should be reporting bugs or if this is "as designed"!
-mwt
Answers
-
mwt,
sqlcl just calls the vault rest apis which probably means there's something there that isn't working. Can you verify the vault cli works from your machine to the remote machine? If that works, what are the commands in sqlcl that are showing a 400 error?
-kris
-
Try to integrate vault in Nodejs application using "node-vault