Table of contents:

Fugo's TV Dashboards feature can capture a login-protected dashboard, report, or URL and keep it up to date on your screens automatically, including dashboards secured with Okta. To do that, Fugo needs to sign in on a schedule the same way you do - and if your Okta account uses multi-factor authentication, Fugo needs a way to generate a valid code at capture time without a phone in the loop.

That's what this article walks you through: setting up Google Authenticator as a factor on a dedicated Okta account, retrieving the underlying Secret Key (instead of scanning the QR code with a physical device), and handing that key to Fugo so it can generate a fresh code every time it refreshes your dashboard.

We've built Dashboards so your credentials and data stay secure, but as an extra precaution we strongly recommend using a dedicated, "least-privileged" service account for any dashboard Fugo signs into - typically a read-only account scoped to just the dashboard(s) you want on screen, rather than your own personal or admin login.

You can read more about setting up a service account in Google Workspace here; the same principle applies whether your dashboard sits behind Okta, Google, or Microsoft.

Okta doesn't hand you a "Secret Key" by that name - it's the same underlying value an authenticator app like Google Authenticator uses to generate its 6-digit codes, and Okta will show it to you as text as long as you skip the QR-code scan step. The walkthrough below gets you there.

This part happens once, at the org level, and needs an Okta admin.

1. In the Okta Admin Console, click Admin and verify your identity if prompted.

2. Go to Security and click Enable Authenticators.

3. Click Add Authenticator.

4. Find Google Authenticator in the list and click Add.

5. Confirm by clicking Add again.

Now switch to the service account itself (or sign in as it) to enroll the factor you just enabled:

6. Click Settings from the account menu.

7. In the Security Methods pane, click Set up next to Google Authenticator.

8. Verify your identity when prompted.

9. Click Set up to begin enrolling Google Authenticator.

10. You'll be shown a QR code to scan - instead, click Can't scan. This is the step that matters: it reveals the actual Secret Key as plain text rather than a QR code.

11. Copy the code shown and save it somewhere safe - this is the Secret Key you'll enter into Fugo.

Okta will also ask you to confirm the enrollment in an authenticator app; if you're doing that verification step with Google Authenticator on your phone, open the app, tap the plus button, and choose Enter a setup key to paste in the same code.

12. Enter the 6-digit code your authenticator app generates back into Okta to finish verification.

Once enrollment is confirmed, you're done on the Okta side - keep that Secret Key handy for the next step.

With your Secret Key in hand, go to Dashboards in Fugo and add a new dashboard using the matching app card, or the Custom URL card if your dashboard doesn't have a dedicated one.

Enter your dashboard's URL, then set the Authentication Method dropdown to Okta.

This reveals fields for Username, Password, and Secret Key - fill in your service account's credentials and paste in the Secret Key you just saved.

Fugo will generate your login steps automatically from what you've entered, and it will regenerate a fresh 6-digit code from your Secret Key every time it refreshes the dashboard.

Some Okta setups redirect you to a separate sign-in domain (for example, your company's own Okta subdomain) before landing on the dashboard itself. If Fugo's automatic login isn't reaching the right sign-in page, use the Login URL override field under the dashboard's advanced settings to tell Fugo exactly which URL to sign in at before it navigates to your dashboard's own address.

Dashboard stopped capturing after working fine before: if the Secret Key was regenerated in Okta (for example, after a factor reset or a security review), the old key stored in Fugo will no longer produce valid codes - repeat the steps above to get the current key and update it on the dashboard in Fugo.

Service account got locked out: this is usually caused by removing and re-adding the Okta Verify (push) method on the same account - see the Pro Tip above. Contact your Okta admin to unlock the account rather than repeating the change.

Login succeeds in a browser but fails in Fugo: double check the service account actually has permission to view the dashboard you're trying to capture, and that the Login URL override (if you're using one) points to the correct sign-in page.

If you're having trouble connecting your Okta-protected dashboard, reach out to our team at support@fugo.ai or start a chat with us via the chatbox in Fugo CMS.