Authenticate Yaak requests to Ping Advanced Identity Cloud using a service account access token
A Yaak authentication plugin for Ping Advanced Identity Cloud (PingOne AIC).
It uses a service account ID and private key to get an access token, caches it, and sends it as
Authorization: Bearer <token>. It follows the
JWT bearer flow described by Ping.
Use it to call AIC REST APIs such as /am/*, /openidm/* and /environment/*.
Install it from Yaak’s plugin directory, or with the Yaak CLI:
yaak plugin install @jmkraut/pingaic-access-token
.jwk) and note
its ID.| Field | Value |
|---|---|
| Tenant FQDN | Your tenant’s own FQDN, e.g. openam-example.forgeblocks.com. Don’t use a custom domain. A full URL is also accepted. |
| Service Account ID | The service account’s UUID. |
| Private Key | The contents of the .jwk file, or the path to it (~ is supported). A PEM key is also accepted. |
| Scopes | Space-separated, e.g. fr:am:* fr:idm:* or fr:idc:esv:*. They must be a subset of the scopes granted to the service account. |
Any field can use Yaak environment variables, for example ${[ PING_TENANT ]}.
Keep the key out of shared workspaces. Auth settings are saved with the request, folder or workspace. If you sync the workspace to git, a pasted key would be committed too. Use a file path or a Yaak secret/environment variable instead.
iss/sub set to the service account ID and aud set to the token endpoint is
signed with RS256. It is exchanged at
https://<tenant>:443/am/oauth2/access_token using client_id=service-account. The token
request goes through Yaak, so your proxy and certificate settings apply.[pingaic] in Yaak’s plugin log show whether each request used a cached
token or fetched a new one.From the auth tab’s menu:
The plugin is built with the Yaak CLI
(npm install -g @yaakapp/cli).
git clone https://github.com/jmkraut/pingaic-access-token.git
cd pingaic-access-token
yaak plugin dev # rebuild on every change
yaak plugin build # one-off build into build/
To load your local copy, add this folder in Yaak under Settings → Plugins. Yaak reloads the plugin after each rebuild.
Building doesn’t need npm install. The tests and type-check do:
npm install
npm test # vitest
npm run typecheck # tsc; yaak plugin build doesn't check types