niteshift-<task-id>, lowercased with _ replaced by -. Every start and resume registers a fresh node, and Tailscale removes the old
one.
Declare the federated identity’s client ID and the tags its nodes advertise in the environment’s
committed settings.yaml. Both keys are required, tags is a non-empty list of tag:<name>
values, and no other keys are accepted:
settings.yaml
api.tailscale.com/<clientId>, so there is no audience setting.
The issuer and subject don’t depend on the audience. Run this in the Niteshift terminal tab to see
them before you have a client ID:
- Add each tag to
tagOwnersin the policy file, and grant the tags only the access tasks need. - In Trust credentials, add an
OpenID Connect credential with Custom issuer. Enter the inspected
issas Issuer URL and the entire inspectedsubas Subject. Leave Audience blank and remove the empty Custom claims row; Continue stays disabled until you do. - On the Scopes page, choose Custom scopes, then Keys > Auth Keys > Write, and
select the tags from
settings.yaml. - Copy the generated Client ID into
clientId.
sub has the form org:<org_id>:environment:<environment_id>. A subject ending in * trusts
every environment in the organization; use the exact value. Copying an environment gives the copy a
new sub. Create a separate trust credential for the copy and put its client ID in the copy’s
settings.yaml, so the original keeps working.
New tasks join automatically. In a running task, run ns tailscale configure in the Niteshift
terminal tab to join or leave the tailnet according to the current settings. If an existing task
still doesn’t join, start a new task; tasks created before Tailscale support can’t join.
Each task appears in Machines once it joins. Task
nodes are preauthorized and skip device approval, so the tags and your policy file control what
they can reach. If a
task fails to join, the token exchange error shows on the credential in Trust credentials.
Some environment types don’t support Tailscale. In those, tasks don’t join the tailnet, and
ns tailscale configure reports that Tailscale isn’t supported.
When network egress is restricted, Niteshift allows *.tailscale.com automatically, and tailnet
traffic goes through Tailscale’s DERP relays. See Tailscale’s workload identity federation
guide and
tags for the Tailscale-side setup.