# okta Published articles for okta. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How to answer the identity questions on an enterprise security questionnaire DevFeed: [How to answer the identity questions on an enterprise security questionnaire]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-09-14T00:00:00Z Content type: article Language: en Sources: [WorkOS Blog]() Topics: [Security](), [Single sign-on (SSO)](), [Provisioning](), [OpenID connect (OIDC)](), [App]() Tags: [configuration](), [enterprise](), [how-to](), [identity](), [integration](), [oidc](), [okta](), [provisioning](), [saml](), [security](), [sign-in](), [sso]() ### AI overview A practical guide to answering identity-related questions in enterprise security questionnaires. It explains what reviewers are really assessing behind SAML single sign-on and SCIM provisioning questions, including implementation details such as per-organization configuration, certificate rotation, and reliable deprovisioning. ### Source excerpt Every line has a literal answer and a real question behind it. Here is what the buyer is actually checking, which answers you can buy, and the three you cannot fake. ## Three identity vendors shipped the same agent access pattern in eight days DevFeed: [Three identity vendors shipped the same agent access pattern in eight days]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-09-04T16:24:43Z Content type: article Language: en Sources: [WorkOS Blog]() Topics: [Auth0](), [Authorization](), [MCP](), [OpenID connect (OIDC)](), [Single sign-on (SSO)](), [Model Context Protocol]() Tags: [anthropic-claude](), [api](), [auth0](), [authorization](), [cross-app-access](), [identity](), [mcp](), [oidc](), [okta](), [sso]() ### AI overview Okta, Auth0, and Descope shipped implementations of the Cross App Access agent-access pattern between August 24 and September 1. The pattern uses a Client ID Metadata Document to identify calling software and an ID-JAG token exchange to let an identity provider control application access. ### Source excerpt Okta, Auth0, and Descope all shipped Cross App Access between August 24 and September 1. The two-layer pattern underneath it outlasts whichever vendor wins. ## How Does CockroachDB Automate SQL User Lifecycle Management? DevFeed: [How Does CockroachDB Automate SQL User Lifecycle Management?]() Original publisher: [Read original article]() Author: Pritesh Lahoti,Biplav Saraf,Sourav Sarangi Published: 2026-08-28T00:00:00Z Content type: tutorial Language: en Sources: [Cockroach Labs]() Topics: [CockroachDB](), [IAM](), [identity and access management](), [active directory](), [Entra ID](), [okta](), [Microsoft]() Tags: [active-directory](), [cockroachdb](), [entra-id](), [iam](), [identity-and-access-management](), [microsoft](), [okta]() ### AI overview The article addresses how CockroachDB automates SQL user lifecycle management and notes that large enterprises commonly rely on identity provider and identity and access management platforms such as Okta, Microsoft Entra ID, Microsoft Active Directory, and Ory. ### Source excerpt Fortune 1000 enterprises widely rely on major Identity Provider (IdP) and Identity and Access Management (IAM) platforms like Okta, Microsoft Entra ID, Microsoft Active Directory, and Ory. ## Add Cross App Access to Your OIDC Resource Application DevFeed: [Add Cross App Access to Your OIDC Resource Application]() Original publisher: [Read original article]() Author: Sohail Pathan Published: 2026-08-24T05:00:00Z Content type: tutorial Language: en Sources: [Okta Developer]() Topics: [OpenID connect (OIDC)](), [API](), [Authorization](), [JSON Web Tokens](), [Single sign-on (SSO)](), [OAuth 2.0]() Tags: [api](), [authorization](), [cross-app-access](), [jwt](), [oauth-2-0](), [oidc](), [okta](), [scopes](), [sso](), [token](), [xaa]() ### AI overview This guide explains how OIDC-federated applications can support Cross App Access (XAA) for API access on behalf of users. It covers validating and redeeming the ID-JAG, resolving users from claims, issuing access tokens, updating authorization server metadata, and testing the end-to-end flow. ### Source excerpt If you currently federate enterprise customers using OpenID Connect (OIDC) and want to allow applications to access your API on behalf of those users, this Cross App Access (XAA) guide is for you. The Identity Assertion Authorization Grant specification, the basis of XAA, was designed with OIDC in mind. Your authorization server already trusts the customer's IdP for single sign-on (SSO), and XAA reuses that same trust for API access. This guide details what you need to support, how to validate the grant, and how to resolve the user at your resource authorization server. Table of Contents How XAA in OIDC works Analyzing the ID-JAG claims XAA implementation checklist for OIDC-federated applications Mapping user identity from iss and sub Validating the ID-JAG and resolving the user Issuing the access token Updating authorization server metadata Making cross-application requests from your OIDC app securely Configure your XAA OIDC Resource app in Okta Create the OIDC requesting app for testing Create the OIDC resource app in Okta Register and configure the AI Agent in Okta Verify your Okta XAA setup on xaa.dev Configure OIDC SSO Verify the refresh token exchange for an ID-JAG token Redeem the ID-JAG for an access token at the resource authorization server Call the resource API with the access token Prove the XAA connection end-to-end Takeaways for implementors who also have SAML apps Learn more about Cross App Access, OIDC, and OAuth 2.0 How XAA in OIDC works When an agent (like one running in Claude) needs API access, it presents an Identity Assertion Authorization Grant (ID-JAG). The ID-JAG is a short-lived JSON Web Token (JWT) issued by the customer's Identity Provider (IdP) for your authorization server. Your resource server accepts the token, identifies the user, and issues your own access token, all while leaving the customer's existing OIDC integration untouched. The sequence diagram shown below describes the OIDC XAA flow. Notice that the OIDC SSO flow stays the ## I Found My Coordinates: Code, Community, and Okta DevFeed: [I Found My Coordinates: Code, Community, and Okta]() Original publisher: [Read original article]() Author: Vanshika Pandey Published: 2026-08-20T05:00:00Z Content type: opinion Language: en Sources: [Okta Developer]() Topics: [Development](), [Software Engineering](), [Google]() Tags: [advocacy](), [community](), [developer](), [google](), [hackathons](), [javascript](), [journey](), [networking](), [okta](), [security](), [work]() ### AI overview A personal account of developing a career through campus ambassador work, internships, community building, developer advocacy, and software development. ### Source excerpt It all started with a phone call from an institute that reached out to recruit me for its campus ambassador program. I was navigating my first year of college, figuring things out. It was all new for me, a new city, far from home, and a hostel room. I was not aware of anything except books and lectures. A senior at my campus ambassador program advised me to create a LinkedIn account and start looking for opportunities from day one. As they say, "You don't have to be great to start, but you have to start to be great." So I started applying for random internships. Soon, I received my first offer, where I discovered the power of networking and community. "No one can whistle a symphony. It takes a whole orchestra to play it." - H.E. Luccock Community has always been the best part of my life. The love and support we receive from each other are invaluable. I have always given to the community and gained far more in return. I attended an institution that wasn't particularly well-known. There weren't many communities, so why not do something about it? Through professional platforms, I discovered Google Developer Student Clubs (GDSC), researched the opportunity, and applied. I became the pioneer GDSC Lead at my institution, and one of 280 leads across India. We built the community from scratch, organizing meetups, workshops, and hackathons that delivered real value to students. These experiences sparked curiosity and helped students find their voice. When I stumbled across the Developer Advocate role, I was very happy and curious, so I started digging into it. My journey into advocacy "What you seek is seeking you." - Rumi One day, I got an email from a founder who said he liked my LinkedIn profile and wanted me to join his organization as a Developer Advocate - that moment was surreal. That's how I landed an internship as a Developer Advocate at Zuplo, where I learned something crucial: to understand developers' pain points, I needed to walk in their shoes. To truly advocat ## Okta Cross App Access (XAA / ID-JAG) in Nirmata AIControls: standards-based authorization for AI agents DevFeed: [Okta Cross App Access (XAA / ID-JAG) in Nirmata AIControls: standards-based authorization for AI agents]() Original publisher: [Read original article]() Author: Ritesh Patel Published: 2026-08-19T00:24:40Z Content type: article Language: en Sources: [Nirmata]() Topics: [cross-app-access](), [Authorization](), [okta](), [Artificial Intelligence](), [Model Context Protocol (MCP)](), [Large Language Model](), [JSON Web Tokens](), [OAuth]() Tags: [ai](), [authorization](), [cross-app-access](), [engineering](), [jwt](), [llm](), [mcp](), [mcp-server](), [oauth](), [okta](), [standards]() ### AI overview The article explains how Nirmata AIControls supports Okta Cross App Access and the ID-JAG authorization profile for AI agents. It describes token exchanges performed on behalf of agents, administrator-controlled app-to-app access, policy checks, budgets, and audit records for delegated MCP and LLM calls. ### Source excerpt AIControls now performs the ID-JAG token exchanges on your agents' behalf -- so agents need no protocol code -- and policy-checks, budgets, and attributes every delegated MCP and LLM call to the human it acts for. ID-JAG answers may this agent act for this user? AIControls answers what... The post Okta Cross App Access (XAA / ID-JAG) in Nirmata AIControls: standards-based authorization for AI agents first appeared on Nirmata. ## Migrating Live Enterprise SCIM Directories to WorkOS with SCIM Bridge DevFeed: [Migrating Live Enterprise SCIM Directories to WorkOS with SCIM Bridge]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-14T00:00:00Z Content type: tutorial Language: en Sources: [WorkOS Blog]() Topics: [migration](), [Provisioning]() Tags: [architecture](), [bridge](), [database](), [migration](), [okta](), [provisioning](), [proxy](), [rollback]() ### AI overview The article presents SCIM Bridge, a reversible migration proxy for moving live enterprise directories from a home-grown SCIM endpoint to WorkOS Directory Sync. It describes dual-writing, backfilling, verification, staged authority, and rollback before final cutover. ### Source excerpt How SCIM Bridge moves live enterprise directories onto WorkOS Directory Sync with zero downtime, staged authority, and lossless rollback until the last step. ## Vercel Passport is now generally available DevFeed: [Vercel Passport is now generally available]() Original publisher: [Read original article]() Author: Yanick Bélanger Published: 2026-07-31T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Authentication](), [Entra ID](), [OpenID connect (OIDC)](), [JSON Web Tokens](), [Back end](), [Deployment]() Tags: [authentication](), [backend](), [entra-id](), [jwks](), [oidc](), [okta](), [payload](), [scope](), [vercel](), [verify]() ### AI overview Vercel Passport is generally available for protecting Vercel deployments with Okta, Microsoft Entra ID, or another OIDC provider. It provides verified visitor identity to application code, supports group-based authorization, enables token verification in downstream services, and records successful authentications in activity and audit logs. ### Source excerpt Vercel Passport is now generally available. Passport allows you to protect your Vercel deployments with your own identity provider. Visitors authenticate through Okta, Microsoft Entra ID, or any OIDC provider before viewing a protected deployment, and Vercel forwards a signed identity token to the deployment so application code can build on who the visitor is. Read visitor identity in application code The getIdentity() helper in @vercel/passport reads the Vercel request context and returns the authenticated visitor. Vercel strips client-supplied values for the x-vercel-oidc-passport-token header and injects the verified token after Passport validates the session, so the identity your code receives is already verified. The subject field is a stable identifier for the visitor, scoped to your team and the Vercel Connect application that links Passport to your identity provider, and externalSubject is the visitor's ID in the provider itself. The helper returns null only when a request arrives without a Passport session, because unauthenticated browser visitors are redirected to the identity provider before they ever reach your code. In local development, getIdentity() returns a configurable development identity, so the same code path works without a real identity provider. Authorize with groups from your identity provider The signed Passport token can now carry additional identity claims from your provider, such as group membership. Request the groups scope and allowlist the claim in the Vercel Connect application that Passport uses, then read it from the identity payload: The additional identity scopes documentation covers provider configuration, including a full Okta walkthrough. Verify identity in downstream services Forward the Passport token from your application to another backend as a bearer token and verify it there with verifyIdentity(), available in @vercel/passport 1.0.0 and later. The helper checks the token signature, the Passport claims, and that the token ## Vercel Passport is now in Public Beta DevFeed: [Vercel Passport is now in Public Beta]() Original publisher: [Read original article]() Author: Andrew Qu Published: 2026-06-17T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [OpenID connect (OIDC)](), [JSON Web Tokens](), [Auth0](), [Deployment]() Tags: [deployment](), [enterprise](), [external](), [identity](), [oidc](), [okta](), [token](), [vercel]() ### AI overview Vercel Passport is in public beta, allowing enterprise teams to protect Vercel deployments with their own identity provider through OIDC authentication. ### Source excerpt Enterprise teams can now control access to their Vercel deployments with Vercel Passport, using their own identity provider. Visitors authenticate through providers like Okta, Auth0, or any compatible OIDC provider before they can view a protected deployment. Use Passport to: Reuse an OIDC application across multiple projects Set a team default that applies to new projects automatically Assign Passport to existing projects in bulk After Passport authenticates a visitor, Vercel injects a signed JWT into the x-vercel-oidc-passport-token request header. Read it server-side to access the external_sub claim, the stable visitor identifier returned by your identity provider: Read the documentation to get started. Read more ## Zero Trust VPN and networking guide for business security teams DevFeed: [Zero Trust VPN and networking guide for business security teams]() Original publisher: [Read original article]() Published: 2025-09-23T18:03:01Z Content type: tutorial Language: en Sources: [Learn on Tailscale]() Topics: [zero trust networking](), [Virtual Private Network](), [Security](), [Business Security](), [tailscale](), [Authorization](), [Single sign-on (SSO)](), [okta](), [Google](), [Microsoft]() Tags: [authorization](), [entra-id](), [google](), [implementation](), [networking](), [okta](), [security](), [teams](), [vpn](), [zero-trust]() ### AI overview This guide explains Zero Trust networking as an approach that verifies users and devices for each access request, applies least privilege and segmentation, and limits lateral movement. It compares this model with traditional VPN access and describes how Tailscale uses identity, device posture, authorization, SSO, and SSH features to support Zero Trust principles. ### Source excerpt Learn how Zero Trust works and why it beats traditional VPNs for business security. Get implementation tips, compare solutions, and discover how to limit access without killing productivity. ## Speedrun Incident Investigations Across GitHub, AWS, Okta, and More DevFeed: [Speedrun Incident Investigations Across GitHub, AWS, Okta, and More]() Original publisher: [Read original article]() Author: jpitts@goteleport.com (Jack Pitts) Published: 2025-09-05T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [incident](), [Security](), [Amazon Web Services](), [GitHub](), [okta](), [audit](), [SIEM, Security, Observability]() Tags: [api-keys](), [audit](), [aws](), [cloud](), [cloud-infrastructure](), [github](), [incident](), [logs](), [okta](), [security](), [visibility]() ### AI overview This tutorial explains how security teams can investigate identity-related incidents across GitHub, AWS, Okta, and other systems by correlating activity and audit data. It describes the limits of fragmented logs, SIEMs, and CNAPPs, and introduces examples for tracing access pathways and incident scope. ### Source excerpt Security teams spend hours stitching logs during investigations. Learn to investigate identity threats in minutes with full visibility across GitHub, AWS, and Okta. ## Integrating OpenID Connect with Redpanda DevFeed: [Integrating OpenID Connect with Redpanda]() Original publisher: [Read original article]() Author: Ben Barkhouse Published: 2025-09-02T00:00:00Z Content type: tutorial Language: en Sources: [Redpanda]() Topics: [OpenID connect (OIDC)](), [Single sign-on (SSO)](), [Authentication](), [Authorization](), [Docker Compose](), [Security](), [Command-line interface](), [Entra ID]() Tags: [authentication](), [authorization](), [cli](), [compose](), [docker](), [entra-id](), [oidc](), [okta](), [open-source](), [openid-connect](), [redpanda-api](), [redpanda-console](), [security](), [sso](), [tutorial]() ### AI overview A tutorial on configuring OpenID Connect authentication and single sign-on for Redpanda. It explains OIDC's relationship to OAuth 2.0, supported identity providers and deployment options, API availability limitations, and a local Docker Compose setup using Keycloak, Redpanda Console, and a Redpanda cluster. ### Source excerpt Learn how to set up OpenID Connect with Redpanda to protect your critical data from unauthorized access. ## One Year Later: Signing CISA's Secure by Design Pledge DevFeed: [One Year Later: Signing CISA's Secure by Design Pledge]() Original publisher: [Read original article]() Published: 2025-06-10T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard](), [cisa](), [cve remediation](), [container images](), [MFA](), [Security](), [Single sign-on (SSO)](), [passwords](), [chainguard vms](), [ssh]() Tags: [authentication](), [chainguard](), [chainguard-containers](), [chainguard-vms](), [cisa](), [container-images](), [cve](), [cve-remediation](), [mfa](), [okta](), [password](), [passwords](), [secure-by-design](), [secure-by-design-pledge](), [secure-software](), [security](), [shift-left](), [ssh](), [sso](), [vulnerabilities](), [vulnerability-management]() ### AI overview Chainguard reviews its progress one year after signing CISA's Secure by Design pledge, including CVE remediation across its container images, company-wide MFA through Okta SSO, and password-free access with automated SSH key provisioning for Chainguard VMs. ### Source excerpt Chainguard signed CISA's Secure by Design pledge in 2024. One year later, we look at progress we've made in key areas like CVE remediation and disclosures. ## Zero-Trust Access for GitHub DevFeed: [Zero-Trust Access for GitHub]() Original publisher: [Read original article]() Author: ben@goteleport.com (Ben Arent) Published: 2025-02-20T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [GitHub](), [Zero Trust](), [MFA](), [Security](), [Authentication](), [certificates](), [audit](), [Logging](), [okta](), [Entra ID]() Tags: [audit](), [authentication](), [certificates](), [github](), [idp](), [logging](), [mfa](), [okta](), [security](), [terraform](), [zero-trust]() ### AI overview The article explains Teleport's approach to securing GitHub repositories with zero-trust access. It describes risks from SSH keys, personal access tokens, and identity-provider compromise, and presents hardware MFA, short-lived certificates, and audit logging as part of a defense-in-depth model. ### Source excerpt Learn how to secure GitHub repos with zero-trust principles using Teleport's GitHub Proxy Support, hardware MFA, short-lived certificates, and audit logging. ## Why "why" is the wrong question to be asking after incidents with Dennis Henry of Okta DevFeed: [Why "why" is the wrong question to be asking after incidents with Dennis Henry of Okta]() Original publisher: [Read original article]() Published: 2024-04-29T15:52:48Z Content type: article Language: en Sources: [The incident.io Blog]() Topics: [incident](), [incident management](), [Incident response]() Tags: [incident](), [incident-channel](), [incident-management](), [incident-response](), [learning](), [okta](), [outage](), [post-mortem](), [safety](), [slack-incident]() ### AI overview This episode of The Debrief features Dennis Henry of Okta discussing why asking "how" after an incident is more useful than asking "why." The conversation focuses on examining contributing factors, reducing blame, improving learning, and supporting psychological safety. ### Source excerpt In this episode of The Debrief, we chat with Dennis Henry of Okta about why "how" is a much better question to ask after incidents. ## Practical Authorization Patterns for Small Teams DevFeed: [Practical Authorization Patterns for Small Teams]() Original publisher: [Read original article]() Author: Matt Boyle Published: 2024-04-04T00:00:00Z Content type: tutorial Language: en Sources: [Encore Updates]() Topics: [Authorization](), [Access Control](), [Security](), [Architecture & Design]() Tags: [access-control](), [auth0](), [authorization](), [kubernetes](), [okta](), [patterns](), [security]() ### AI overview This article explains how small teams can implement authorization effectively before their products grow. It distinguishes authorization from authentication and discusses practical patterns such as RBAC, auditing strategies, and considerations for scaling permissions. ### Source excerpt Practical patterns for implementing authorization ## Enforcing device trust on code changes DevFeed: [Enforcing device trust on code changes]() Original publisher: [Read original article]() Author: Griffin Choe Published: 2023-12-08T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Device Trust](), [Figma](), [GitHub](), [Security](), [pull-requests](), [Single sign-on (SSO)](), [WebAuthn](), [OAuth](), [ssh](), [Cryptography]() Tags: [cryptographic](), [device-trust](), [encryption](), [figma](), [git](), [github](), [oauth](), [okta](), [pull-requests](), [security](), [security-engineering](), [ssh](), [sso](), [verification]() ### AI overview Figma's security engineering team describes enforcing device trust for code changes merged into GitHub release branches. The approach combines commit signature verification with Okta Device Trust certificates to ensure changes originate from trusted, company-managed devices, while addressing risks from leaked credentials, tokens, and SSH keys. ### Source excerpt Here's how the Figma security engineering team leveraged commit signatures and Okta Device Trust certificates to protect GitHub release branches. ## Blog: Using Falco to Create Custom Identity Detections DevFeed: [Blog: Using Falco to Create Custom Identity Detections]() Original publisher: [Read original article]() Published: 2023-11-28T00:00:00Z Content type: article Language: en Sources: [Falco - Falco](), [Falco - The Falco blog]() Topics: [Falco](), [okta](), [Security](), [threat detection](), [audit](), [password reset](), [account takeover](), [Threat Research]() Tags: [architecture](), [audit](), [blog](), [event-source](), [falco](), [identity](), [okta](), [password-reset](), [security](), [threat-detection]() ### AI overview This blog post explains how the open-source Falco Okta plugin can support Identity Threat Detection and Response by analyzing Okta audit logs. It describes default rules, adaptable rule logic, and a custom rule example focused on password-reset activity and potential account takeover. ### Source excerpt Identity Threat Detection & Response (ITDR) in the cloud is of paramount importance to limit access to sensitive data and maintain the integrity of cloud infrastructure. Leading cloud providers like AWS, Microsoft Azure, and Google Cloud have implemented robust Identity and Access Management (IAM) controls, as well as Multi-Factor Authentication (MFA) options, to ensure that users have the standardized access control limitations. However, as the saying goes, "Trust, but verify." Even with these layers of security, there's a growing concern about what happens when a rogue employee or an external adversary manages to compromise an identity provider. Recent months have witnessed a surge in attacks targeting popular identity providers like Okta, underscoring the critical need for timely and effective detection capabilities. In fact, (Crowdstrike's 2023 Threat Hunting) report had classified 62% of all interactive cyber intrusions as having involved some form of compromised identities. Without proper detection, incidents such as the attacks on organizations like Caesars and MGM might go unnoticed until it's too late. Fortunately, open source Falco offers a Dedicated plugin for the Okta identity platform, empowering security teams to respond swiftly and with the context required to take real action against potential threats. In this blog post, we will delve into how Falco fulfills the requirements for ITDR capabilities. We'll illustrate the significance of Falco's adaptable rule logic and provide readers with a real-world example of crafting custom rules derived directly from Okta audit logs. Understanding the rule logic The Falco Okta plugin comes with a set of valuable default rules for Okta logs, which are designed to assist you in enhancing the security of your Okta platform. A typical illustration of the importance of these rules lies in the process of initiating a password reset within the Okta platform. In practice, an insider threat might reset a password, opt not ## Application and AI roundup - October DevFeed: [Application and AI roundup - October]() Original publisher: [Read original article]() Author: Adam Published: 2023-11-09T00:00:00Z Content type: article Language: en Sources: [Shostack & Friends Blog]() Topics: [Application Security](), [Artificial Intelligence](), [Security](), [Vulnerabilities](), [Adversarial attacks](), [Large Language Model](), [browser](), [okta](), [solarwinds]() Tags: [ai](), [appsec](), [article](), [attacks](), [browser](), [large-language-models](), [okta](), [security](), [solarwinds](), [vulnerabilities]() ### AI overview An October roundup covering the SEC's case against SolarWinds and its CISO, research on vulnerabilities in large language models and adversarial attacks, AI policy and model behavior, and threat-modeling issues involving browser privacy, Okta's support system, and bug hunting. ### Source excerpt Exciting news from the SEC, lots of AI, and lots of threat modeling. ## Teleport 13: New Features and Updates DevFeed: [Teleport 13: New Features and Updates]() Original publisher: [Read original article]() Author: kenneth.dumez@goteleport.com (Kenneth DuMez) Published: 2023-05-10T00:00:00Z Content type: release Language: en Sources: [Teleport]() Topics: [configuration](), [Load Balancing](), [Amazon Web Services](), [Kubernetes](), [okta](), [opensearch](), [TLS (Transport Layer Security)](), [Web]() Tags: [announcement](), [aws](), [configuration](), [kubernetes](), [load-balancing](), [new-features](), [okta](), [opensearch](), [tls](), [ui]() ### AI overview Teleport 13 introduces automatic agent updates with configurable maintenance windows, TLS routing through AWS application load balancers for Server Access and Kubernetes Access, Okta application and group imports, and AWS OpenSearch support for Database Access. Several features are marked as preview releases. ### Source excerpt An overview of all of the new features added to Teleport 13. Automatic Updating, Light Theme and more! ## How to Configure SSO for Amazon RDS Authentication and Authorization DevFeed: [How to Configure SSO for Amazon RDS Authentication and Authorization]() Original publisher: [Read original article]() Author: info@goteleport.com (Janakiram MSV) Published: 2022-05-13T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [Amazon RDS](), [Single sign-on (SSO)](), [Authorization](), [okta](), [saml](), [Authentication](), [Amazon Web Services](), [PostgreSQL](), [Amazon EC2]() Tags: [amazon-rds](), [authentication](), [authorization](), [aws](), [how-to](), [okta](), [policies](), [postgresql](), [saml](), [security](), [sso](), [tutorial]() ### AI overview A tutorial explains how to configure single sign-on for Amazon RDS using Okta, SAML, and Teleport. It shows how to map Okta groups to Teleport roles and use role-based access control to restrict access to specific databases, including a sensitive forecast database. ### Source excerpt This post is a tutorial to set up single sign-on (SSO) for Amazon RDS access ## Tutorial: How to Configure SSO for AWS Resources with Okta and SAML DevFeed: [Tutorial: How to Configure SSO for AWS Resources with Okta and SAML]() Original publisher: [Read original article]() Author: info@goteleport.com (Janakiram MSV) Published: 2022-03-29T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [Single sign-on (SSO)](), [Amazon Web Services](), [okta](), [saml](), [Amazon EC2](), [ssh](), [VPC]() Tags: [aws](), [ec2](), [how-to](), [okta](), [saml](), [ssh](), [sso](), [tutorial]() ### AI overview This tutorial explains how to configure single sign-on for AWS resources using Okta, SAML, and Teleport. It demonstrates fine-grained SSH access to EC2 instances by mapping Okta users and groups to infrastructure roles and access policies. ### Source excerpt This post explains how to configure SSO for AWS Resources with Okta and SAML. ## Single sign-on user experience challenges and integration approaches DevFeed: [Single sign-on user experience challenges and integration approaches]() Original publisher: [Read original article]() Author: ben@goteleport.com (Ben Arent) Published: 2022-03-11T00:00:00Z Content type: article Language: en Sources: [Teleport]() Topics: [Single sign-on (SSO)](), [User experience (UX)](), [identity and access management](), [OpenID connect (OIDC)](), [saml](), [okta](), [Terraform]() Tags: [authentication](), [identity](), [identity-and-access-management](), [oidc](), [okta](), [saml](), [sso](), [terraform](), [ux]() ### AI overview This article examines user-experience problems with single sign-on, including repeated authentication prompts and redirect flows. It explains how application architectures and integrations using SAML or OIDC make a standardized sign-on experience difficult, and discusses identity-provider, access-control, and automation practices. ### Source excerpt A deep dive into the UX of current single sign-on and an overview of possible solutions. ## Modern IT (information technology) DevFeed: [Modern IT (information technology)]() Original publisher: [Read original article]() Author: info@goteleport.com (Travis Gary) Published: 2021-10-13T00:00:00Z Content type: opinion Language: en Sources: [Teleport]() Topics: [information-technology](), [Automation](), [DevOps](), [okta](), [Terraform]() Tags: [automation](), [company](), [devops](), [experience](), [growth](), [information-technology](), [okta](), [remote](), [self-service](), [support](), [systems](), [technology](), [terraform]() ### AI overview Travis shares Teleport's approach to running IT for a fast-growing global remote company. The article argues for automation, employee self-service, and DevOps-style IT operations to reduce support requests and preserve employee agility. ### Source excerpt Running IT at a fast-growing company presents many challenges. Travis shares his experience managing the IT team at Teleport. [Next page]()