OC Authentication Helper

Secure authentication to multiple OpenShift clusters using curl requires retrieving OAuth tokens from the correct cluster context and injecting them into request headers. This Skill automates token retrieval via oc whoami -t, selects the active cluster context, and injects the Authorization: Bearer header into curl commands while preventing token exposure in logs or command history.

Yes. Instead of manually fetching tokens with oc whoami -t and building Authorization headers, prefix your curl command with this Skill to automatically retrieve the token for your current cluster context, inject it securely into the request, and execute the API call—eliminating manual token handling and exposure risk.

Token exposure in scripts occurs when tokens are echoed, logged, or stored in plain text. This Skill prevents exposure by retrieving tokens internally, injecting them directly into curl headers, and ensuring tokens never appear in command output or shell history while maintaining full authentication.

You need the OpenShift CLI (oc) installed, configured kubeconfig with cluster contexts, and access to the target OpenShift cluster. This Skill uses oc to discover contexts and retrieve tokens, then passes them securely to curl for API authentication across any configured cluster.

Yes. This Skill seamlessly handles multi-cluster environments by discovering available contexts in kubeconfig, selecting the correct cluster context, and retrieving that context's OAuth token to authenticate requests to any configured OpenShift cluster (such as app.ci or dpcr).

Manual token injection is repetitive, error-prone, and creates security risks: tokens may leak into logs or history. An authentication helper centralizes token retrieval and injection, eliminates code duplication across commands, prevents token exposure, and simplifies authenticated API calls across multiple clusters.