Okta SSO sessions and app sessions run on different clocks
Okta SSO and your app's local session are independent. Learn how to align timeouts and force re-auth for sensitive OIDC routes.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Okta SSO and your app's local session are independent. Learn how to align timeouts and force re-auth for sensitive OIDC routes.
Swap static cloud access keys in GitHub Actions for short-lived OIDC tokens, with constraints, an AWS trust-policy example, and validation steps.
Stop using client secrets in your SPAs. Learn how to implement Okta's OIDC Authorization Code Flow with PKCE to secure your web application without compromising credentials.
An architecture note on wiring Rancher 2.x to a SAML or OIDC identity provider: the minimal design, trust boundaries around etcd, verification steps, and the failure modes that actually bite.
Guide to choosing Teleport's RBAC source: static local roles vs OIDC/JWT‑derived roles, with a comparison table, trade‑offs, and step‑by‑step OIDC setup.
Learn how to implement Google Cloud Pub/Sub push subscriptions to eliminate polling overhead, secure endpoints with OIDC tokens, and manage reliability using dead-letter topics.
Replace long‑lived cloud credentials in GitHub Actions with a short‑lived OIDC token. Minimal design, claim‑based trust, operational checks, and failure modes explained for AWS, GCP, and Azure.
Okta's recommended SPA login is OIDC Authorization Code flow with PKCE. Here's the setup, a working okta-auth-js example, and the token-storage trade-off you need to decide on deliberately.
GitHub Actions can mint short-lived OIDC tokens that cloud providers exchange for temporary credentials — no stored secrets. The security lives in the cloud-side trust condition, not the token.