Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/guidewire-install-auth

@820dfc8
Run it yourself

Authenticate production Guidewire Cloud API integrations and survive the auth-side failures — token expiry storms, scope drift, private-CA PKIX errors, secret rotation. Use when hardening OAuth2 token caching, configuring JVM trust stores, or rotating client secrets without downtime. Trigger with "guidewire auth", "guidewire OAuth2", "guidewire token cache", "guidewire PKIX", "guidewire secret rotation".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/guidewire-install-auth

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesAPI_REFERENCE.md

≈1.4k tokens on demand. Your agent reads this file only when SKILL.md points to it.

Guidewire Cloud API — Auth Reference

Endpoint catalog and response shapes for the auth-side of Cloud API integration. Operational patterns (caching, rotation, recovery) live in SKILL.md; this document is the static reference.

OAuth2 token endpoint

POST https://hub.[TENANT].guidewire.net/oauth/token
Content-Type: application/x-www-form-urlencoded

Request body (URL-encoded):

Field Required Notes
grant_type yes always client_credentials for service apps
client_id yes from GCC > Identity & Access > Applications
client_secret yes rotatable; supports dual-secret window during rotation
scope yes space-separated tenant-configured scope strings

Response (200 OK):

{
  "access_token": "eyJhbGciOi...",
  "token_type": "Bearer",
  "expires_in": 3600,
  "scope": "pc.account.read pc.account.write"
}

expires_in is advisory; the JWT's exp claim is authoritative. Decode and use exp for cache-expiry math, not Date.now() + 3600 * 1000. Clock skew between the runtime and Hub is the most common cause of premature 401.

Error responses (400):

{ "error": "invalid_client", "error_description": "..." }
{ "error": "invalid_scope", "error_description": "..." }
{ "error": "invalid_grant", "error_description": "..." }

invalid_grant indicates the secret was rotated and the runtime still holds the old value — fall back to the secondary secret per dual-secret pattern, or trigger a controlled restart if no secondary is configured.

JWT structure (decoded)

A typical Guidewire-issued JWT decodes to (header omitted):

{
  "iss": "https://hub.[TENANT].guidewire.net",
  "sub": "[client-id]",
  "aud": ["pc", "cc", "bc"],
  "exp": 1735689600,
  "iat": 1735686000,
  "scope": "pc.account.read pc.account.write cc.claim.read",
  "tenant": "[tenant-slug]"
}

Validate aud matches the product you are calling (calling PC with a token whose aud lacks pc returns 401 even with valid scopes). Validate scope contains every required scope on every refresh — this is the scope-drift gate.

Verification probe (CI smoke test)

GET https://[TENANT].guidewire.net/pc/rest/v1/account/v1/accounts?pageSize=1
Authorization: Bearer [token]

Returns 200 OK with the canonical Cloud API response envelope. Use this in CI as a deploy-gate: a deploy that cannot list accounts has broken auth and should not pass the gate.

{
  "count": 42,
  "data": [
    {
      "attributes": { "accountNumber": "A000001", "accountStatus": { "code": "Active" } },
      "checksum": "abc123",
      "links": { "self": { "href": "/account/v1/accounts/pc:8001" } }
    }
  ],
  "links": { "next": { "href": "/account/v1/accounts?pageSize=1&offsetToken=..." } }
}

HTTP status code matrix (auth-relevant)

Status When Action
200 on /oauth/token normal token issuance cache and reuse
400 on /oauth/token invalid_client, invalid_scope, invalid_grant inspect error field, do not retry blindly
429 on /oauth/token thundering-herd refresh single-flight gate is missing or broken; fix the cache
500/502/503 on /oauth/token transient Hub or upstream issue retry with exponential backoff, max 3 attempts
401 on Cloud API token expired, audience mismatch, or scope no longer issued proactive refresh window prevents most expiry cases; verify aud claim
403 on Cloud API least-privilege violation do not retry; alert and re-issue with corrected role assignment in GCC
409 on Cloud API stale checksum (not auth) covered in guidewire-sdk-patterns
TLS handshake failure private-CA chain not trusted install CA at JVM/init-container layer

Domain conventions reference

Pattern Domain Used for
gcc.guidewire.com *.guidewire.com Console UI; tenant administration; app registration
hub.[TENANT].guidewire.net *.guidewire.net OAuth2 token issuance
[TENANT].guidewire.net/pc/rest/v1 *.guidewire.net PolicyCenter Cloud API runtime
[TENANT].guidewire.net/cc/rest/v1 *.guidewire.net ClaimCenter Cloud API runtime
[TENANT].guidewire.net/bc/rest/v1 *.guidewire.net BillingCenter Cloud API runtime

Egress firewalls must allow *.guidewire.net for runtime APIs; *.guidewire.com egress is only required for tools that hit the console (CLI utilities, infrastructure-as-code that registers apps). A common misconfiguration is allowing only *.guidewire.com and seeing every Cloud API call fail at DNS resolution.

Authorization Code flow (Jutro browser apps)

This skill covers Service Application (Client Credentials) flow only. Browser applications using Jutro frontends use the Authorization Code flow with PKCE, which requires session/cookie handling outside the scope of a backend integration. Treat that as a separate integration shape.

Reference: RFC 7636 — PKCE and the Guidewire Cloud Platform Identity Federation guide on the developer portal.

Related references

  • references/implementation-guide.md — extended walkthrough with environment-specific notes
  • Sibling skill guidewire-sdk-patterns — REST client patterns, retry/backoff, error mapping
  • Sibling skill guidewire-security-and-rbac — secret-store architecture, audit trail, PII handling

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill provides production-grade instructions and code patterns for authenticating with Guidewire Cloud APIs. It follows security best practices, such as using secret management tools like SOPS instead of hardcoding credentials, implementing proper token caching to avoid rate-limiting, and handling certificate trust issues at the JVM level. All network operations target well-known Guidewire service domains.

  • Socket2mo

    1 alert: gptAnomaly

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 3 months ago
What it can do
Reads files Edits files Runs commands
version
1.26.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
compatibility
Designed for Claude Code
All 9 allowed tools
ReadWriteEditBash(curl:*)Bash(jq:*)Bash(java:*)Bash(keytool:*)Bash(openssl:*)Grep
Other metadata
tags
[
  "guidewire",
  "oauth2",
  "authentication",
  "token-management",
  "secret-rotation",
  "pkix"
]

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/guidewire-install-auth