Would like to know how people are using Grokbot in regards to needing to be connected up to a VPN to access work sites (I.e. JIRA), as well as other login methods like SSO, Passkey and physic keys like YubiKey.
I need to be connected to a VPN to access JIRA as well use those other login methods to access Dev and QA Salesforce orgs.
Hey @Diego_Delgado, thanks for the question!
Grok Bot’s computer runs in the cloud with its own internet connection, so it can’t join your corporate VPN today. Sites that are only reachable on the VPN (like an internal Jira) won’t be accessible from its browser yet. Better support for private networks is something the team is actively looking at. One caution in the meantime: please don’t ask the Bot to install a VPN client on its own computer, as that can knock the computer offline.
What does work today:
If your Jira is Atlassian Cloud (a yourcompany.atlassian.net address that works from a normal browser off the VPN), the Bot can use it: connect it from the Connectors page or have the Bot open it in its browser and sign in.
The Bot can also run tasks on your own computer through the desktop app (Settings, then “Execution on Local Computer”, with per-action review). Since your machine is on the VPN, the Bot can reach internal services from there, for example, through Jira’s API or command line tools.
For SSO: fully supported. When the Bot hits a sign-in page, it pauses and asks you to take over its browser; you log in yourself (including through Okta or another identity provider), and it continues from there.
All that said, if your organization restricts logins to your corporate network’s IP addresses, the same VPN limitation applies for now.
Hardware keys like YubiKey also work on macOS and Windows: in Grok Bot’s Settings, find the Security Key section and turn on “Use hardware security keys”. The key stays plugged into your computer and you approve each use. So for your Salesforce Dev and QA orgs, sign-in should work as long as the orgs themselves are reachable from the internet.