惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
MongoDB | Blog
MongoDB | Blog
博客园_首页
博客园 - 三生石上(FineUI控件)
博客园 - 聂微东
B
Blog RSS Feed
D
Docker
IT之家
IT之家
大猫的无限游戏
大猫的无限游戏
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
阮一峰的网络日志
阮一峰的网络日志
罗磊的独立博客
Recent Announcements
Recent Announcements
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
A
About on SuperTechFans
The GitHub Blog
The GitHub Blog
G
Google Developers Blog
V
V2EX
量子位
雷峰网
雷峰网
月光博客
月光博客
云风的 BLOG
云风的 BLOG
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
T
Tailwind CSS Blog

Cerbos - All Posts

Authentik vs Keycloak: Self-hosted IdP comparison Mapping business requirements to authorization policy for automotive Fine-grained authorization for AI gateways EIC 2026: Stop counting agents, protect what they can touch Agent skill for writing authorization policies in Claude Desktop Identity security in 2026 EIC 2026 takeaways: the identity stack built for humans will not hold up for AI agents Already have authentication? Here's the authorization layer you still need. Tokens are authorization decisions: a guide to policy-driven token issuance What is a Runtime Authorization Platform It's a dimmer switch, not a kill switch. How CISOs are rethinking AI agent governance From maps to bitmaps (and from bitmaps to bitmaps) AuthZEN, Shared Signals, SCIM Events, IPSIE: Notes from the OpenID Enterprise Panel How do you update authorization policies without redeploying your application? IIW42 recap: Where agent authorization got real Cerbos PDP v0.52.0/v0.53.0: Engine performance, security hardening, and CEL path functions Authorization Management Platforms: what they do, how they work, and where they fit PocketOS AI coding agent deleted a production database in 9 seconds Non-Human Identity management still has a blind spot Supabase alternative in 2026: Best open source auth options Benefits of on-premise authorization: Why enterprises are moving toward self-hosted Authorization policies: How to write, test, and validate them (faster with AI) Agent skill for writing authorization policies How much does it cost to build authorization in-house? Why centralized authorization governance reduces incident response time OPA alternative Why AI agents make authorization a right now problem Modernizing legacy application authorization: why it’s your biggest security blind spot How to add authorization to legacy applications without code changes 5 authorization blind spots auditors find, and how to fix them
Using WorkOS SSO with Cerbos
Alex Olivier · 2022-03-03 · via Cerbos - All Posts

Single Sign-On (SSO) is the most frequently occurring requirement for enterprise organisations looking to adopt new SaaS applications. WorkOS is single integration which enables your application to support SSO for all of the most popular identity providers.

As identity is such a key part to authorization, today we released a starter project that connects WorkOS and Cerbos. It demonstrates how an identity object, passed from WorkOS, can be mapped into the principal information in the call to Cerbos. By doing this, all the profile information can be used, regardless of the source, to define policies and conditions.

The benefit of integrating an authentication and identity provider with Cerbos is that the rich context about the user can be used in policy conditions. It enables going beyond simplistic role-based access controls (RBAC) to more complex attribute-based access control (ABAC) without the need to have complicated logic written directly in your code.

Cerbos integrates with many authentication providers. Our WorkOS integration works with the same principle that all of our other Authentication integrations (Okta, Auth0, FusionAuth etc). It relies on getting the identity object and combining it with the resource that user is trying to access and ask the question whether that user is allowed to do that action on the said principal. For example, “can a user who is a manager in the northeast region approve an expense report that belongs to an employee from the south region in the amount of $5000?”

WorkOS with cerbos

Following is an example of what this may look like in your application code. It simply grabs the profile from WorkOS and passes it over to Cerbos in the principal object. You can see a full example on GitHub.

// get the profile for WorkOS
const { profile } = await workos.sso.getProfileAndToken({
  code,
  clientID,
});

// check access
const authorized = await cerbos.check({
  principal: {
    id: profile.id,
    roles: ["user"], //populate based on your user roles
    attr: profile.raw_attributes,
  },
  resource: ...,
  actions: [...]
})

You can find out more about WorkOS on their site, our integration, as well as our other integrations such as Auth0, Okta and FusionAuth and more on the Ecosystem page.