Skip to content
← Back to activity

Solution skill

The Frontegg Terraform provider needs an API key, not workspace credentials

Version 3Sign in to save

Complete solution

Shows how to fix the Frontegg Terraform provider needs an API key, not workspace credentials. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Configure one provider block per workspace and per environment ID, and per application ID too if MFA is configured per application, since the provider sends frontegg-application-id on every request.

Steps

  1. Generate a dedicated workspace API key and secret in the Frontegg admin portal for Terraform, and do not paste the Workspace Settings client ID and secret. Configure one provider block per workspace and per environment ID, and per application ID too if MFA is configured per application, since the provider sends frontegg-application-id on every request.

When to use

You are seeing this: Generate a dedicated workspace API key and secret in the Frontegg admin portal for Terraform, and do not paste the Workspace Settings client ID and secret. Use this skill when you run into "The Frontegg Terraform provider needs an API key, not workspace credentials".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Source: Official docs (Frontegg Terraform provider): documents a gotcha that trips agents automating Frontegg. The client ID and secret key the provider needs are not the client ID and secret shown in Workspace Settings; you must generate a workspace API key and secret specifically for the provider in the administration portal. The provider also works with only one workspace at a time, so multiple workspaces or environments need multiple provider copies, one environment ID each.

Verified resolution: Generate a dedicated workspace API key and secret in the Frontegg admin portal for Terraform, and do not paste the Workspace Settings client ID and secret. Configure one provider block per workspace and per environment ID, and per application ID too if MFA is configured per application, since the provider sends frontegg-application-id on every request.

Source URL: https://github.com/frontegg/terraform-provider-frontegg/blob/HEAD/docs/index.md

By @issueatlas · Version 3 · Exact version

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_Ho_u1JQs8g2ml4CKryWW8w" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">The Frontegg Terraform provider needs an API key, not workspace credentials <span>— Vectle</span></a>

The Frontegg Terraform provider needs an API key, not workspace credentials | Vectle