Connect Okta to GitHub Copilot
Give GitHub Copilot governed access to Okta through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Okta to GitHub Copilot in four steps
Admins approve the server once. Everyone in GitHub Copilot then gets it through the same governed connection.
- 1
Approve Okta in Runlayer
Add Okta from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect GitHub Copilot to Runlayer
GitHub Copilot gets connector tools through the Runlayer Plugin, and reaches Okta’s tools through the plugin’s search and execute tools.
GitHub Copilot setup guide - 3
Sign in to Okta
An admin adds Okta credentials to Runlayer once. They never sit in the client’s configuration.
- 4
Use Okta from GitHub Copilot
Okta’s approved tools appear in GitHub Copilot. Every call is checked against policy and recorded.
Tools
Okta tools in GitHub Copilot
Okta reports its tools when your organization connects it, so the list depends on your deployment.
Control
What Runlayer can see and stop in GitHub Copilot
Some controls apply to every client at the gateway. Others depend on what GitHub Copilot exposes to Runlayer.
Gateway policy (available)
Every Okta call from GitHub Copilot passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, GitHub Copilot as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for GitHub Copilot yet, so control happens at the gateway.
Frequently asked questions
Connect more