You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Oracle integration works only in the authenticated proxy mode. Start a local proxy for connections to your Oracle database by using the command below:
507
+
507
508
```
508
-
tsh proxy db --tunnel --port 1521 --db-user=<user> --db-name=<db-name> oracle
509
+
> tsh proxy db --tunnel --port 11555 --db-user=<user> --db-name=<db-name> oracle
510
+
511
+
Started authenticated tunnel for the Oracle database "oracle" in cluster "teleport.example.com" on 127.0.0.1:11555.
509
512
```
510
513
511
514
<Noticetype="tip">
512
-
This command uses the local port 1521, but you can choose any port, or let
513
-
`tsh` pick a local port at random if you omit the `--port` flag.
514
-
You should specify a port to avoid the need to reconfigure your GUI client again
515
-
later.
515
+
The command above uses the local port 11555, but you can choose any available port. Leaving `--port` empty will cause `tsh` to pick a random one.
516
+
</Notice>
517
+
518
+
The local proxy supports TCP and TCPS modes. Different clients prefer different modes.
519
+
520
+
TCP:
521
+
- requires no username or password
522
+
- generally easier to configure
523
+
524
+
TCPS:
525
+
- requires no username or password
526
+
- depends on automatically created wallet
527
+
- uses JDBC URL for configuration
528
+
529
+
<Noticetype="warning">
530
+
Teleport versions earlier than 17.2.0 support only a limited range of clients and only offer TCPS mode. `tsh` will automatically detect this situation and warn the user. We recommend updating to the latest version of Teleport to access full client support and additional connection options.
516
531
</Notice>
517
532
533
+
### Oracle SQL Developer (standalone)
534
+
518
535
In "Connections" click the "+" button for a new database connection:
0 commit comments