Exploring the future of identity: https://xitter.cf/t.co/zl6VJ52QaD Community Discord: https://xitter.cf/t.co/JRJtt0m020

Joined October 2020
Auth0 Lab retweeted
excited to share that @mattkrzus has joined the @auth0lab team Matt's a hardcore ML systems engineer and I'm very excited he's part of the team we believe using AI to secure AI will be a big part of the future, so more of our experiments will involve ML. go give him a follow!
2
1
15
1,048
Auth0 Lab retweeted
I'm hiring a Principal Applied AI/ML Scientist for the @auth0lab team. this is a first for our team we are currently focused on enabling builders and companies of any size to ship production grade AI agents, by helping them with identity and security. we believe data, and developing our own models will play a huge role in this if you are great at ML and would love to work with a small team on taking ideas from 0 to 1: okta.com/company/careers/eng… DMs open for questions
7
12
3
85
12,461
Auth0 Lab retweeted
Camp AI is going on tour 🌎 6 cities. 5 months. Startup demos, panels, and ghost stories about what your agents did when no one was watching. First stop: SF on May 7. NYC, London, and more soon! Presented by @Auth0. Will add links in 🧵as we announce each city! #Auth0CampAI
3
4
3
10
2,287
Someone please solve auth for agents.
101
14
10
283
43,905
Auth0 Lab retweeted
agent identity and access control is a big problem. openclawd makes it very evident :) a lot moltbook not knowing who is behind usage is that a lot of keys are api keys vs user bound tokens. there's no openclawd account (nor should there be just for its own sake). identity is relevant and necessary depending on use cases. rate limiting is a very common use case to push for identity but the question becomes: what do you limit on? e.g. can someone have 1000 clankers if they are a "real person" and is each unlimited? does a person get a quota and the quota gets split amongst clankers? the identity approach you choose depends on what you need it for. @worldnetwork real world identity comes in handy (much like @X verification) because you want to baes it on real world scarcity, not just an agent's "private key" btw @auth0 we’ve done a bunch of stuff with auth0.ai and there is more coming. if you are dealing with agents, auth, identity, access control hmu. would love to chat
Moltbook voting can’t distinguish between • 1 person running 1,000 molts • 1,000 molts run by 1,000 different people Prove ownership over your agent swarms with onemolt.ai using World ID. Platforms can verify incoming molts have a human owner and reject misbehaving swarms.
5
3
26
4,062
Auth0 Lab retweeted
❤️ seeing another tech company join the "Labs" trend @GoogleLabs was a pioneer and more recently - @cloudflare has "emerging tech" formerly lead by @dok2001 - @GitHubNext at github - @stripe has a team lead by @jeff_weinstein - at Auth0 we have @Auth0Lab and now @AnthropicAI
Anthropic
@AnthropicAIJan 13
We’re expanding Labs—the team behind Claude Code, MCP, and Cowork—and hiring builders who want to tinker at the frontier of Claude’s capabilities. Read more: anthropic.com/news/introduci…
2
3
1
28
5,012
Auth0 Lab retweeted
Today is a great day for open standards and AI, and at @Auth0, we’re all in on both. We’re excited to join the Agentic AI Foundation (AAIF) with @Okta and keep working with the community to help builders create safer, more capable AI systems.
Today we launch the Agentic AI Foundation (AAIF) with project contributions of MCP (@AnthropicAI), goose (@blocks) and AGENTS.md (@OpenAI), creating a shared ecosystem for tools, standards, and community-driven innovation. Learn more about this major step toward: hubs.la/Q03Xvw3v0
2
1
9
3,600
Auth0 Lab retweeted
sign in with @vercel enables every dev to build on top of the AI cloud naturally, builders using @auth0 will be able to support it for their apps @nextjs app with "Sign in with Vercel" 👇. thanks @okbel for the last mile assist! code for `setup_auth0_vercel.sh` in reply
1
10
1
35
7,572
Auth0 Lab retweeted
another year, another @auth0lab team offsite (+ featured guests) extremely happy and grateful to have met these folks 10+ years ago and to continue working with them ❤️ we miss you @woloski
6
2
38
2,691
🚀 Just launched: aistandards.directory The ecosystem of agentic AI protocols and standards is expanding rapidly: MCP, A2A, AP2, XAA... Things are moving fast. This directory helps you keep up.
1
4
1
12
1,922
Auth0 Lab retweeted
there are many issues here one or them the tool is doing auth via hardcoded api keys, not getting tokens scoped to users per tx (eg via oauth) @auth0 can help address this, both token vault and potentially async authz (depending on implementation)
we hijacked microsoft's copilot studio agents and got them to spill out their private knowledge, reveal their tools and let us use them to dump full crm records these are autonomous agents.. no human in the loop #DEFCON #BHUSA @tamirishaysh
1
2
5
1,622
Auth0 Lab retweeted
if you look at the ChatGPT agent demo, you quickly realize it needs to log into sites on your behalf to get stuff done @auth0 we are working on solving this problem, securely hmu if you want to chat, DMs are open
Today we launched a new product called ChatGPT Agent. Agent represents a new level of capability for AI systems and can accomplish some remarkable, complex tasks for you using its own computer. It combines the spirit of Deep Research and Operator, but is more powerful than that may sound—it can think for a long time, use some tools, think some more, take some actions, think some more, etc. For example, we showed a demo in our launch of preparing for a friend’s wedding: buying an outfit, booking travel, choosing a gift, etc. We also showed an example of analyzing data and creating a presentation for work. Although the utility is significant, so are the potential risks. We have built a lot of safeguards and warnings into it, and broader mitigations than we’ve ever developed before from robust training to system safeguards to user controls, but we can’t anticipate everything. In the spirit of iterative deployment, we are going to warn users heavily and give users freedom to take actions carefully if they want to. I would explain this to my own family as cutting edge and experimental; a chance to try the future, but not something I’d yet use for high-stakes uses or with a lot of personal information until we have a chance to study and improve it in the wild. We don’t know exactly what the impacts are going to be, but bad actors may try to “trick” users’ AI agents into giving private information they shouldn’t and take actions they shouldn’t, in ways we can’t predict. We recommend giving agents the minimum access required to complete a task to reduce privacy and security risks. For example, I can give Agent access to my calendar to find a time that works for a group dinner. But I don’t need to give it any access if I’m just asking it to buy me some clothes. There is more risk in tasks like “Look at my emails that came in overnight and do whatever you need to do to address them, don’t ask any follow up questions”. This could lead to untrusted content from a malicious email tricking the model into leaking your data. We think it’s important to begin learning from contact with reality, and that people adopt these tools carefully and slowly as we better quantify and mitigate the potential risks involved. As with other new levels of capability, society, the technology, and the risk mitigation strategy will need to co-evolve.
2
6
20
4,559
Auth0 Lab retweeted
if you are are an @auth0 customer and want to allow web AI agents (like @OpenAI Operator) to access your site securely and do stuff on behalf of users, DM me working on something ;)
2
1
1
10
1,802
Auth0 Lab retweeted
want some feedback 🙏 I’ve been thinking about auth for AI agent interactions for a while. think client agent -> server agent came up with a set of 6 problems to solve in question form 👇 are these right? what other important ones are missing? 1️⃣ Authentication: How does the server agent know who is trying to perform an action? 2️⃣ Delegation: Is the agent acting on its behalf, or on behalf of a user? On behalf of another agent? 3️⃣ Consent: If the client is acting on behalf of a user, how does the user consent to this operation? 4️⃣ Authorization: How does the server agent know if the caller can perform the action (e.g., call a specific tool)? If the client is acting on behalf of a user, is the user authorized to perform this action? 5️⃣ Auth for headless agents (agents without a UI): How should AI agents without a UI authenticate users? 6️⃣ Fine-grained authorization: How do we ensure AI agents only have the permissions they need to perform their task, and not more?
18
6
1
30
4,507
Auth0 Lab retweeted
Auth doesn't help create 🔥 AI demos. but it does help make your AI agent prod ready this is why we @auth0 are partnering with @googlecloud to secure Agent2Agent (A2A) authentication What's the Agent2Agent protocol? A2A is a new open interoperability protocol created by @googlecloud, and launched a month ago, with support and contributions from 60+ companies. It aims to allow agents to communicate with other agents regardless of their implementation framework or tech stack. For example, a “client” agent should be able to communicate with server agents implemented with @langchain LangGraph, @crewAIInc, @vercel @aisdk, @CloudflareDev agents SDK, and any other agentic framework, or any agent implemented without one. Why is auth important for AI Agents? As companies and devs deploy AI agents into production, interactions between these agents will be common. And naturally, these interactions need to be secure. Auth is a big part of security. What are we partnering on? A2A is being designed to support enterprise-grade authentication and authorization from day one. We are working with @googlecloud to define A2A auth specs based on secure standards and build SDKs and code samples that showcase A2A auth capabilities, including how to integrate A2A with @auth0 and our new product Auth for GenAI, providing both great security and great auth UX. Headless agent auth One thing we have also been exploring with the Google Cloud team is how agents that don't have a UI (“headless agents”) should authenticate users. For these scenarios, we believe the Client Initiated Backchannel Authentication (CIBA) flow will be a very valuable tool for developers and architects. CIBA is an OpenID Connect flow that does not rely on redirects in the user's browser. Instead, Agents can reach out to users outside via push notification, email, SMS, etc., for them to authenticate. A Working Sample Enough chat, let's see a demo :) Imagine a scenario where: 1. John Doe, who works at Staff0, wants to open a bank account by talking to a chatbot agent 2. Because of internal policies, the bank agent needs to verify that the user is an employee at Staff0, so it contacts the Staff0 HR agent. 3. The Staff0 HR agent can use the Staff0 HR API to check if the user is an employee or not. We've worked with the Google Cloud A2A team to build a demo showcasing these capabilities 👇 Link to repo and full blog post with more details in reply
7
16
2
78
8,229
Auth0 Lab retweeted
🚨big MCP news! new auth spec is in. how does it work? 4️⃣ steps the MCP server is now a "resource server" in oauth parlance (think API), so: 1️⃣ MCP client makes first request to MCP server 2️⃣ MCP server tells clients how they can authenticate to it with a file like this 👇 at a well known location 3️⃣ the MCP client then reaches out to authorization_servers to authenticate and obtain credentials (think a jwt access token, could be others) side note: @auth0 we are looking forward to being used as the authorization server for a lot of MCP servers. if you are interested in protecting your MCP server with @auth0 DM me :) 4️⃣ the MCP client then calls MCP server tools authenticating with the credentials from 3️⃣ this was a great industry wide collaboration that greatly improves the protocol! big 👏 to @dsp_ for shepherding this through blog post from Den Delimarsky with more details about the protocols involved in reply (I took the screenshot from it)
12
20
6
73
16,755
Auth0 Lab retweeted
MCP is not just an API wrapper. it’s a way to provide ANY context to an LLM want great DX and have IDEs support features past a model’s cutoff date? MCP‼️ demo: @github pull request tool with @cursor_ai @vercel @aisdk @auth0 how? custom MCP server by @jcenturion86
13
15
4
133
26,872
Auth0 Lab retweeted
want to easily build AI chatbots that connect to enterprise apps? with @aisdk + @auth0 auth for genai it's a piece of cake. @box integration 👇 cc @levie
2
8
1
33
4,140
Auth0 Lab retweeted
The official @auth0 MCP Server is live 🚀 If you're using Claude Desktop, @cursor_ai, @windsurf_ai and other MCP Clients— this is for you: 🛠️ 20+ operations ready 🛡️ Secure auth w/ scopes + session mgmt ⚡️ Quick setup with 'npx@auth0/auth0-mcp-server init'
1
24
3
120
12,432
the @auth0 MCP server is now available. feels great to see this come to life! 🚀 🛠️ 20+ operations 🛡️ secure auth flow w/ scopes and session management ⚡️ quick setup for Claude Desktop, @cursor_ai and @windsurf_ai get started with `npx @auth0/auth0-mcp-server init`
devs using @auth0 should be able to ask: "I want to create a mobile app with passkey and Google Sign-In, and access to an API with these scopes…" and we'd just set everything up for them with the new official @auth0 MCP server, you can 💪 @cursor_ai demo 📺👇, link in reply
1
5
21
1,582