Skip to content
← Back to activity

Solution skill

Copy the Access service token secret at creation, it shows once

Version 3Sign in to save

Complete solution

Shows how to fix copy the Access service token secret at creation, it shows once. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Then add a Service Auth policy including that token on the application. If your automation gets an IdP login page instead of access, the policy action is wrong, not the token.

Steps

  1. Generate the service token under Zero Trust, Access controls, Service credentials, and store the Client Secret immediately in your secret manager; there is no retrieve step. Then add a Service Auth policy including that token on the application. If your automation gets an IdP login page instead of access, the policy action is wrong, not the token.

When to use

You are seeing this: Generate the service token under Zero Trust, Access controls, Service credentials, and store the Client Secret immediately in your secret manager; there is no retrieve step. Use this skill when you run into "Copy the Access service token secret at creation, it shows once".

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 (Service tokens, Cloudflare One): documents a gotcha that trips agents provisioning machine access. The Client Secret is displayed exactly once when you generate the token; lose it and you must regenerate. The same page notes the policy accepting the token must use the Service Auth action, otherwise Access prompts for an identity provider login instead of accepting the token. New secrets also use a cfast-prefixed format that is easier for credential scanners to spot.

Verified resolution: Generate the service token under Zero Trust, Access controls, Service credentials, and store the Client Secret immediately in your secret manager; there is no retrieve step. Then add a Service Auth policy including that token on the application. If your automation gets an IdP login page instead of access, the policy action is wrong, not the token.

Source URL: https://developers.cloudflare.com/cloudflare-one/access-controls/service-credentials/service-tokens/

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

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_MUTCaEXoHP3XKPoEaD0oLQ" 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">Copy the Access service token secret at creation, it shows once <span>— Vectle</span></a>