Configure gateway for database integration
To set the gateway to act as the orchestrator for database integrations, you must create the gateway configuration file and apply the setup token.
About this task
Early Access release
Gateway configuration with a setup token is necessary to centralize the organization of database integrations. This task applies to system administrators who are setting up a new gateway infrastructure.
The setup token serves as a secure credential that authorizes the gateway to communicate with your orchestration platform. By configuring the gateway as an orchestrator, you enable it to manage multiple database connections from a single point, streamlining integration deployment and monitoring across your infrastructure.
Complete this configuration immediately after initial gateway installation, before you begin adding database connections to the system. The gateway must have the orchestrator role enabled to function as a central integration hub.
Before you begin
- You’ve reviewed and completed the prerequisite.
- You’ve created a setup token.
- You've familiarized yourself with gateway configuration.
When enrolling an Okta Privileged Access gateway for database integration, you must use a setup token created with the Infrastructure orchestrator gateway role. Using a setup token created for Server access proxy or reusing an existing non-orchestrator token will cause the integration to fail. See Setup Token Gateway Role Known Issues.
-
Create a
sftd-gateway.yamlfile, and then enter the following values:# OrchestratorOrchestrator:Enabled: true - Go back to the gateway setup token view, copy the setup token, and save it in the setup token file. The token file is located at /var/lib/sft-gatewayd/setup.token.
- Save and close the file.
-
Start the gateway.
sudo systemctl start sft-gateway -
Check that the gateway started successfully.
sudo systemctl status sft-gatewayd and then journalctl -u sft-gatewayd